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-next>] [day] [month] [year] [list]
Message-ID: <aW-Rd8bQQ_ODMXeV@wieczorr-mobl1.localdomain>
Date: Tue, 20 Jan 2026 14:34:30 +0000
From: Maciej Wieczor-Retman <m.wieczorretman@...me>
To: Dave Hansen <dave.hansen@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, sohil.mehta@...el.com, 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
Subject: Re: [PATCH 4/6] x86/cpu: Add platform ID to CPU info structure

On 2026-01-19 at 11:50:55 -0800, Dave Hansen wrote:
>
>From: Dave Hansen <dave.hansen@...ux.intel.com>
>
>The end goal here is to be able to do x86_match_cpu() and match on a
>specific platform ID. While it would be possible to stash this ID
>off somewhere or read it dynamically, that approaches would not be
>consistent with the other fields which can be matched.
>
>Read the platform ID and store it in cpuinfo_x86->x86_platform_id.
>
>There are lots of sites to set this new field. Place it near
>the place c->microcode is established since the platform ID is
>so closely intertwined with microcode updates.
>
>Note: This should not grow the size of 'struct cpuinfo_x86' in
>practice since the u8 fits next to another u8 in the structure.
>
>Signed-off-by: Dave Hansen <dave.hansen@...ux.intel.com>
>Cc: Thomas Gleixner <tglx@...nel.org>
>Cc: Ingo Molnar <mingo@...hat.com>
>Cc: Borislav Petkov <bp@...en8.de>
>Cc: Dave Hansen <dave.hansen@...ux.intel.com>
>Cc: "H. Peter Anvin" <hpa@...or.com>
>Cc: Tony Luck <tony.luck@...el.com>
>Cc: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
>Cc: "Peter Zijlstra (Intel)" <peterz@...radead.org>
>Cc: x86@...nel.org
>Cc: Jon Kohler <jon@...anix.com>
>---
>
> b/arch/x86/include/asm/processor.h |    1 +
> b/arch/x86/kernel/cpu/common.c     |    4 +++-
> b/arch/x86/kernel/cpu/intel.c      |    1 +
> 3 files changed, 5 insertions(+), 1 deletion(-)
>
>diff -puN arch/x86/include/asm/processor.h~cpu-x86_stepping arch/x86/include/asm/processor.h
>--- a/arch/x86/include/asm/processor.h~cpu-x86_stepping	2026-01-19 11:38:09.341914025 -0800
>+++ b/arch/x86/include/asm/processor.h	2026-01-19 11:38:09.444917962 -0800
>@@ -140,6 +140,7 @@ struct cpuinfo_x86 {
> 		__u32		x86_vfm;
> 	};
> 	__u8			x86_stepping;
>+	__u8			x86_platform_id; /* Intel-only. 3 bits */

Should platform ID be added to print_cpu_info()?

So it's printed alongside (family: 0xN model: 0xN, stepping: 0xN)

-- 
Kind regards
Maciej Wieczór-Retman


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ