[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1ad4500b-0b10-4b89-87c6-e2989425954b@intel.com>
Date: Thu, 29 Jan 2026 13:23:15 -0800
From: Sohil Mehta <sohil.mehta@...el.com>
To: Dave Hansen <dave.hansen@...ux.intel.com>
CC: Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>, "Ingo
Molnar" <mingo@...hat.com>, Jon Kohler <jon@...anix.com>, Pawan Gupta
<pawan.kumar.gupta@...ux.intel.com>, "Peter Zijlstra (Intel)"
<peterz@...radead.org>, Thomas Gleixner <tglx@...nel.org>, Tony Luck
<tony.luck@...el.com>, <x86@...nel.org>, LKML Mailing List
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/6] x86/microcode: Add platform mask to Intel microcode
"old" list
On 1/19/2026 11:51 AM, Dave Hansen wrote:
>
> The Intel "microcode-20250512" release was used to generate the
> existing contents of intel-ucode-defs.h. Use that same release and add
> the platform mask to the definitions.
>
There is an issue in the newly generated list, likely due to a bug in
the generation script. I noticed that some entries are missing.
For example, models 0x46 (Haswell_G) and 0xbe (Alderlake) get deleted in
the diff but do not have a corresponding new entry in the list with
platform ID.
Deleted ones:
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0x45, .steppings = 0x0002, .driver_data = 0x26 },
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0x46, .steppings = 0x0002, .driver_data = 0x1c },
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0x47, .steppings = 0x0002, .driver_data = 0x22 },
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0xbd, .steppings = 0x0002, .driver_data = 0x11f },
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0xbe, .steppings = 0x0001, .driver_data = 0x1d },
> -{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0xbf, .steppings = 0x0004, .driver_data = 0x3a },
Added with platform IDs, but no model 0x46 or 0xbe:
> +{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0x45, .steppings = 0x0002, .platform_mask = 0x72, .driver_data = 0x26 },
> +{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0x47, .steppings = 0x0002, .platform_mask = 0x22, .driver_data = 0x22 },
> +{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0xbd, .steppings = 0x0002, .platform_mask = 0x80, .driver_data = 0x11f },
> +{ .flags = X86_CPU_ID_FLAG_ENTRY_VALID, .vendor = X86_VENDOR_INTEL, .family = 0x6, .model = 0xbf, .steppings = 0x0004, .platform_mask = 0x07, .driver_data = 0x3a },
Powered by blists - more mailing lists