[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08c39a16-a729-44b0-bcd8-d4c6dbada213@intel.com>
Date: Tue, 20 Jan 2026 07:09:01 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Andy Shevchenko <andriy.shevchenko@...el.com>,
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 5/6] x86/cpu: Add platform ID to CPU matching structure
On 1/20/26 00:30, Andy Shevchenko wrote:
...
>> #define X86_STEPPING_ANY 0
>> #define X86_STEP_MIN 0
>> #define X86_STEP_MAX 0xf
>> +#define X86_PLATFORM_ANY 0x0
>> #define X86_FEATURE_ANY 0 /* Same as FPU, you can't test for that */
> Wouldn't it be slightly better to locate the new one here to follow the order
> in x86_cpu_id above?
I stuck it there because ->platform_mask acts functionally like the
stepping mask does.
Powered by blists - more mailing lists