[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240308110043.GEZerv21Qj10Q7-8p5@fat_crate.local>
Date: Fri, 8 Mar 2024 12:00:43 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Kevin Loughlin <kevinloughlin@...gle.com>, acdunlap@...gle.com,
alexander.shishkin@...ux.intel.com, andrisaar@...gle.com,
bhe@...hat.com, brijesh.singh@....com, dave.hansen@...ux.intel.com,
dionnaglaze@...gle.com, grobler@...gle.com, hpa@...or.com,
jacobhxu@...gle.com, jpoimboe@...nel.org, kai.huang@...el.com,
linux-kernel@...r.kernel.org, michael.roth@....com,
mingo@...hat.com, peterz@...radead.org, pgonda@...gle.com,
ross.lagerwall@...rix.com, sidtelang@...gle.com, tglx@...utronix.de,
thomas.lendacky@....com, x86@...nel.org, ytcoode@...il.com
Subject: Re: [PATCH v2] x86/kernel: skip ROM range scans and validation for
SEV-SNP guests
On Fri, Mar 08, 2024 at 11:30:50AM +0100, Ard Biesheuvel wrote:
> Agree with the analysis and the conclusion. However, this will need to
> be split into generic and x86 specific changes, given that the DMI
> code is shared between all architectures, and explicitly checking for
> SEV-SNP support in generic code is not appropriate.
>
> So what we will need is:
I was actually thinking of:
x86_init.resources.probe_roms = snp_probe_roms;
and snp_probe_roms() is an empty stub.
Problem solved without ugly sprinkling of checks everywhere.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists