From: Dylanger Daly <dylangerdaly@protonmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Ryzen 4000 (Mobile) Softlocks/Micro-stutters
Date: Mon, 19 Oct 2020 23:37:06 +0000 [thread overview]
Message-ID: <3pKjdPYCiRimYjqHQP0xd_vqhoTOJqthTXOrY_rLeNvnQEpIF24gXDKgRhmr95JfARJzbVJVbfTrrJeiovGVHGbV0QBSZ2jez2Y_wt6db7g=@protonmail.com> (raw)
In-Reply-To: <2cc5da3e-0ad0-4647-f1ca-190788c2910b@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1898 bytes --]
> Does booting with sched=credit alter the symptoms?
Indeed I've tried this, the result is an observable delay, unusable performance, credit2 seems to be the only usable scheduler, I'm certain it has something to do with SMT being disabled, resulting in 8 cores instead of the expected 16 threads.
> As a random thought, have you tried disabling use of (deep) C-states?
Yeah I've tried both `processor.max_cstate=1|5`
I've also tried adding `0xC0010292` and `0xC0010296` MSRs into arch/x86/msr.c (guest_{rdmsr,wrmsr})
The above allowed me to use https://github.com/r4m0n/ZenStates-Linux/blob/master/zenstates.py
After removing `dom0_max_vcpus=1 dom0_vcpus_pin` from Xen's CMDLINE, and disabling C6 I observed no change.
> This wants reporting (with sufficient data, i.e. at least a serial log)
Hm, I'm not sure there's UART on this Laptop, can I save the boot log somewhere?
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, October 15th, 2020 at 10:57 PM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> On 15/10/2020 01:38, Dylanger Daly wrote:
>
>> Hi All,
>>
>> I'm currently using Xen 4.14 (Qubes 4.1 OS) on a Ryzen 7 4750U PRO, by default I'll experience softlocks where the mouse for example will jolt from time to time, in this state it's not usable.
>>
>> Adding `dom0_max_vcpus=1 dom0_vcpus_pin` to Xen's CMDLINE results in no more jolting however performance isn't what it should be on an 8 core CPU, softlocks are still a problem within domU's, any sort of UI animation for example.
>>
>> Reverting [this commit (8e2aa76dc1670e82eaa15683353853bc66bf54fc)](https://github.com/xen-project/xen/commit/8e2aa76dc1670e82eaa15683353853bc66bf54fc) results in even worse performance with or without the above changes to CMDLINE, and it's not usable at all.
>>
>> Does anyone have any pointers?
>
> Does booting with sched=credit alter the symptoms?
>
> ~Andrew
[-- Attachment #2: Type: text/html, Size: 4135 bytes --]
next prev parent reply other threads:[~2020-10-19 23:37 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 [this message]
2020-10-20 8:15 ` Jan Beulich
2020-12-22 23:04 ` Dylanger Daly
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='3pKjdPYCiRimYjqHQP0xd_vqhoTOJqthTXOrY_rLeNvnQEpIF24gXDKgRhmr95JfARJzbVJVbfTrrJeiovGVHGbV0QBSZ2jez2Y_wt6db7g=@protonmail.com' \
--to=dylangerdaly@protonmail.com \
--cc=andrew.cooper3@citrix.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).