[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aW-i4Sqdkv8qVOtJ@wieczorr-mobl1.localdomain>
Date: Tue, 20 Jan 2026 16:03:20 +0000
From: Maciej Wieczor-Retman <m.wieczorretman@...me>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, 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-20 at 07:13:31 -0800, Dave Hansen wrote:
>On 1/20/26 06:34, Maciej Wieczor-Retman wrote:
>>> __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)
>
>It's not a horrible idea, but it's also relatively worthless compared to
>the other three. I'd certainly take a look at it if someone sent a
>patch, but I'm not really looking to add more to this series that
>doesn't _need_ to be here.
Fair enough, and I suppose if someone really needs this information they can
just read the MSR themselves.
--
Kind regards
Maciej Wieczór-Retman
Powered by blists - more mailing lists