xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dylanger Daly <dylangerdaly@protonmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Ryzen 4000 (Mobile) Softlocks/Micro-stutters
Date: Tue, 22 Dec 2020 23:04:44 +0000	[thread overview]
Message-ID: <T95F2Mi9RUUZ4w2wdeRqqM4uRyKgOFQNyooqEoTTDByK-0t9hZ1izG68lf90iExeYabEPSEv8puUeg0SEJtOmz8vYbVox2za28DXLd_h-_s=@protonmail.com> (raw)
In-Reply-To: <768d9dbb-4387-099f-b489-7952d7e883b0@suse.com>

Hey All,

I think I've narrowed down what could be the issue.

I think disabling SMT on any AMD Zen 2 CPU is breaking Xen's Credit2 scheduler, I can only test on AMD Ryzen 4000 based Mobile CPUs, but I think this is what is causing issues with softlocks/having to pin dom0 1 vcpu.

I'm currently trying to re-enable SMT on Qubes 4.1 (Xen 4.14) and I'll report my findings here.


  reply	other threads:[~2020-12-22 23:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  0:38 Ryzen 4000 (Mobile) Softlocks/Micro-stutters Dylanger Daly
2020-10-15  8:18 ` Jan Beulich
2020-10-15  9:14   ` Dylanger Daly
2020-10-15  9:20     ` Jan Beulich
2020-12-23 15:15       ` Dario Faggioli
2020-10-15 11:57 ` Andrew Cooper
2020-10-19 23:37   ` Dylanger Daly
2020-10-20  8:15     ` Jan Beulich
2020-12-22 23:04       ` Dylanger Daly [this message]
2020-12-23  9:59         ` Jan Beulich
2020-12-23 15:51           ` Dario Faggioli
2020-12-23 22:31             ` Dylanger Daly
2021-01-03  6:40             ` Dylanger Daly
2021-01-04 14:29               ` Jan Beulich
2021-03-16  2:10                 ` Dylanger Daly
2021-03-16  8:02                   ` Jan Beulich
2021-03-19  9:03                     ` Dario Faggioli
2021-03-19 12:45                       ` Dylanger Daly
2021-03-19 13:36                         ` Jan Beulich
2021-06-05  0:46                           ` Dylanger Daly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='T95F2Mi9RUUZ4w2wdeRqqM4uRyKgOFQNyooqEoTTDByK-0t9hZ1izG68lf90iExeYabEPSEv8puUeg0SEJtOmz8vYbVox2za28DXLd_h-_s=@protonmail.com' \
    --to=dylangerdaly@protonmail.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).