From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/CPU/AMD: Perform function calls post ZEN feature check regardless
Date: Tue, 12 Aug 2025 16:56:29 -0500 [thread overview]
Message-ID: <b88e7df1-7946-21cc-db0f-d5ce9dcff9b2@amd.com> (raw)
In-Reply-To: <20250812213718.GIaJu0DgbRbBq2mfDY@fat_crate.local>
On 8/12/25 16:37, Borislav Petkov wrote:
> On Wed, Jul 23, 2025 at 12:01:06PM -0500, Tom Lendacky wrote:
>> Currently, if a ZEN family/model is not recognized in bsp_init_amd(), then
>> function calls after the family/model check are skipped. This can prevent
>> older kernels from enabling features on newer hardware, e.g., unrecognized
>> new hardware won't enable SEV-SNP because bsp_determine_snp() is skipped.
>
> bsp_determine_snp() relies partly on the family detection.
>
> If all you care is calling it even without family detection, why don't you
> pull it up, check c->x86 and be done with it?
ZEN3 and ZEN4 won't be set if we do that and since those families don't
have RMPREAD support, SNP won't get enabled on ZEN3 or ZEN4, so we can't
do that.
And, additionally, now there is tsa_init() and the CPUID_FAULT checks
that will be skipped, too.
>
> But even then: we don't really care about older kernels on newer hardware
> - that's why they get backports. We don't really think about backporting when
> working upstream. Frankly...
Hmmm... i guess? Not sure I 100% agree with that.
>
> So I'm sceptical about this.
Your call.
Thanks,
Tom
>
next prev parent reply other threads:[~2025-08-12 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 17:01 Tom Lendacky
2025-07-23 17:11 ` Tom Lendacky
2025-08-12 21:37 ` Borislav Petkov
2025-08-12 21:56 ` Tom Lendacky [this message]
2025-08-12 22:03 ` Borislav Petkov
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=b88e7df1-7946-21cc-db0f-d5ce9dcff9b2@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--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®