[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <977fd7cb-37ee-44d0-a51e-aa288a77b705@intel.com>
Date: Tue, 20 Jan 2026 07:13:31 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Maciej Wieczor-Retman <m.wieczorretman@...me>,
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 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.
Powered by blists - more mailing lists