[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/SYS+LiPVKit4PR@zn.tnic>
Date: Tue, 21 Feb 2023 11:09:15 +0100
From: Borislav Petkov <bp@...en8.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"Zhang, Rui" <rui.zhang@...el.com>,
"Brown, Len" <len.brown@...el.com>,
"zhang.jia@...ux.alibaba.com" <zhang.jia@...ux.alibaba.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH V2 0/1] x86: cpu topology fix and question on
x86_max_cores
On Tue, Feb 21, 2023 at 10:00:54AM +0100, Peter Zijlstra wrote:
> We really should have added that CPUID uniformity sanity check a long
> while ago :-(
We're pretty much there:
c0dd9245aa9e ("x86/microcode: Check CPU capabilities after late microcode update correctly")
(in tip currently)
It would need to get extended to do it on each CPU during SMP boot.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists