[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260208213735.GCaYkCHz1cxp-Ivm7L@fat_crate.local>
Date: Sun, 8 Feb 2026 22:37:35 +0100
From: Borislav Petkov <bp@...en8.de>
To: Dave Hansen <dave.hansen@...ux.intel.com>
Cc: linux-kernel@...r.kernel.org, sohil.mehta@...el.com,
zhao1.liu@...el.com, "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 Fri, Feb 06, 2026 at 03:14:45PM -0800, Dave Hansen wrote:
> 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-02-06 15:14:23.528790212 -0800
> +++ b/arch/x86/include/asm/processor.h 2026-02-06 15:14:23.567791582 -0800
> @@ -140,6 +140,8 @@ struct cpuinfo_x86 {
> __u32 x86_vfm;
> };
> __u8 x86_stepping;
> + /* Intel-only. 3 bits: */
> + __u8 x86_platform_id;
Can we call this something more generic so that we can do:
/* On Intel: platform ID
/* On AMD: something else
so that we can use this on both vendors?
I don't have any usage in mind on AMD now but it might come in handy some day.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists