linux-kernel - Re: [PATCH v5 07/35] x86: Introduce a centralized CPUID data model

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260129160709.GSaXuFreAkumbetUYJ@fat_crate.local>
Date: Thu, 29 Jan 2026 17:07:09 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Ahmed S. Darwish" <darwi@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	Sean Christopherson <seanjc@...gle.com>,
	David Woodhouse <dwmw2@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Sohil Mehta <sohil.mehta@...el.com>,
	John Ogness <john.ogness@...utronix.de>, x86@...nel.org,
	x86-cpuid@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 07/35] x86: Introduce a centralized CPUID data model

On Mon, Jan 26, 2026 at 02:04:51PM +0100, Ahmed S. Darwish wrote:
> So the root-cause of all these "static" vs. "dynamic" distinctions was to
> catch call sites, at compile-time, when using the wrong CPUID storage
> output type relative to the requested leaf/subleaf.

Hmm, ok, I guess we want to catch stuff like that.

> I'll get rid of this static/dynamic terminology and think of something
> better.

But this is not about static and dynamic - you simply have different subleaf
layouts. And I guess you don't have to call them anything. You simply have
different struct types: leaf_0xd_0, leaf_0xd_1, leaf_0xd_n, ...

And that's fine.

The point being: we want our definitions to be as close to the hw spec
definition as possible. Not invent new things. Just use what the SDM says and
that's it.

Thx.

-- 
Regards/Gruss,
    Boris.

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