[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55f755e9-2712-47d5-82d5-d6e685969461@citrix.com>
Date: Tue, 8 Oct 2024 14:38:17 +0100
From: Andrew Cooper <andrew.cooper3@...rix.com>
To: "Ahmed S. Darwish" <darwi@...utronix.de>, x86-cpuid@...ts.linux.dev,
Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
x86@...nel.org
Cc: Thomas Gleixner <tglx@...utronix.de>, Sohil Mehta
<sohil.mehta@...el.com>, John Ogness <john.ogness@...utronix.de>,
linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] x86-cpuid-db: Release v2.0
On 08/10/2024 2:31 pm, Ahmed S. Darwish wrote:
> to:
>
> /*
> * Leaf 0x0
> * Maximum standard leaf number + CPU vendor string
> */
>
> struct leaf_0x0_0 {
> ...;
> };
>
> /*
> * Leaf 0x7
> * Extended CPU features enumeration
> */
>
> struct leaf_0x7_0 {
> ...;
> };
>
> struct leaf_0x7_1 {
> ...;
> };
>
> Overall, this removes ambiguity for IDs like 0x16, and improves kernel
> code greppability (x86 PQ pending).
So what does leaf 0xd with 62 subleaves look like. Do we really have
one number in hex, and one in decimal?
~Andrew
Powered by blists - more mailing lists