mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
	dave.hansen@linux.intel.com, kernel@gpiccoli.net,
	kernel-dev@igalia.com
Subject: Re: [PATCH] x86/tsc: Add debugfs entry to mark TSC as unstable after boot
Date: Sun, 23 Mar 2025 20:51:02 +0100	[thread overview]
Message-ID: <20250323195102.GDZ-BmJgDWLieuUaJs@fat_crate.local> (raw)
In-Reply-To: <8247f64e-316d-0eca-9e5d-0c63c7dfc862@igalia.com>

On Sun, Mar 23, 2025 at 04:21:44PM -0300, Guilherme G. Piccoli wrote:
> This is great to hear - is there any starting point model that you know
> AMD introduced/is introducing TSC_ADJUST?

Zen5.

> We don't know yet what's going on, some TSC skews reported eventually in
> some machines, in a fleet - but "old" processors, Zen 1st gen.  Once things
> are more clear, definitely could provide a more mature report of the issue.

Sure.

Zen1 should not have TSC problems either. If it does, whack BIOS people.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2025-03-23 19:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 13:27 Guilherme G. Piccoli
2025-03-17 14:35 ` Guilherme G. Piccoli
2025-03-17 18:42   ` H. Peter Anvin
2025-03-21 19:26     ` Guilherme G. Piccoli
2025-03-21 21:19       ` Thomas Gleixner
2025-03-23 17:53         ` Guilherme G. Piccoli
2025-03-23 18:14           ` Borislav Petkov
2025-03-23 19:21             ` Guilherme G. Piccoli
2025-03-23 19:51               ` Borislav Petkov [this message]
2025-03-23 19:59                 ` Guilherme G. Piccoli
2025-03-17 14:40 ` Borislav Petkov
2025-03-17 15:03   ` Guilherme G. Piccoli
2025-03-17 15:14     ` Borislav Petkov
2025-03-17 15:24       ` Guilherme G. Piccoli

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=20250323195102.GDZ-BmJgDWLieuUaJs@fat_crate.local \
    --to=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gpiccoli@igalia.com \
    --cc=hpa@zytor.com \
    --cc=kernel-dev@igalia.com \
    --cc=kernel@gpiccoli.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®