From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Dario Faggioli <dfaggioli@suse.com>
Subject: Re: Ryzen 4000 (Mobile) Softlocks/Micro-stutters
Date: Tue, 16 Mar 2021 09:02:21 +0100 [thread overview]
Message-ID: <4916dec1-1bb9-7e6f-2fe5-577bbab92861@suse.com> (raw)
In-Reply-To: <PGn1fJFla-7vPl7QFdkkBX8ASy2cWw-f2HBW7rWE5KgeFEZ_kNUp8Yq5zMaGyS38wMWofVshR75o1jD1rXZeTWtE8XhKQvEq_Dmgsnu-Uy0=@protonmail.com>
On 16.03.2021 03:10, Dylanger Daly wrote:
> I just wanted to close this off and let everyone know the issue ended up being a faulty/misconfigured HPET clock.
>
> Appending `clocksource=tsc tsc=unstable hpetbroadcast=0` to Xen's CMDLINE totally fixed my issue, I assume Xen was detecting TSC may have been 'off' and was trying to recover/self-correct?
I find this a very confusing combination of command line options.
In particular "tsc=unstable" clears one of the feature prereqs
(TSC_RELIABLE) that are required for "clocksource=tsc" to take
any effect, afaict. I therefore would conclude that you're not
actually running with TSC as the clock source. Did you check the
hypervisor log (which might prove me wrong)?
Jan
next prev parent reply other threads:[~2021-03-16 8:02 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
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 [this message]
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=4916dec1-1bb9-7e6f-2fe5-577bbab92861@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dfaggioli@suse.com \
--cc=dylangerdaly@protonmail.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).