[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXuV1IQYiMyn34ps@lx-t490>
Date: Thu, 29 Jan 2026 18:16:04 +0100
From: "Ahmed S. Darwish" <darwi@...utronix.de>
To: Borislav Petkov <bp@...en8.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 Thu, 29 Jan 2026, Borislav Petkov wrote:
>
> 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.
>
ACK.
Powered by blists - more mailing lists