xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Ryzen 4000 (Mobile) Softlocks/Micro-stutters
Date: Fri, 19 Mar 2021 14:36:22 +0100	[thread overview]
Message-ID: <0e963858-6834-96de-4bf2-956f905160b4@suse.com> (raw)
In-Reply-To: <qcVhNDiGu6deufXzsHKbjEr4n3JuLC2cFNc1ORb02vl1IaPjm-37uFkXANQ-i7v77zP1GFxbYoTEG713C4EyHYBrE5YPvA5bXdPc4Brxg5U=@protonmail.com>

On 19.03.2021 13:45, Dylanger Daly wrote:
> Hi Everyone, I've just confirmed only `tsc=unstable` is required,
> that specific change has fixed the issues I was having on the
> Lenovo X13, I assume this is because Lenovo's Clock isn't correct?

Hard to tell without knowing what actually went wrong. It wasn't
very long ago that we had to fix an issue where iirc a machine
wouldn't even boot because of some strange state firmware put
the TSCs in. We were able to work around this, such that
"tsc=unstable" wouldn't be needed. So while there may indeed be
some oddity with what firmware does, there may also be a way to
work around this. But I guess it would take someone debugging
this on an affected system...

Jan


  reply	other threads:[~2021-03-19 13: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
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 [this message]
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=0e963858-6834-96de-4bf2-956f905160b4@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).