From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Zhang, Rui" <rui.zhang@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"zhang.jia@linux.alibaba.com" <zhang.jia@linux.alibaba.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores
Date: Tue, 21 Feb 2023 11:09:15 +0100 [thread overview]
Message-ID: <Y/SYS+LiPVKit4PR@zn.tnic> (raw)
In-Reply-To: <Y/SIRmCE1KJdsRBT@hirez.programming.kicks-ass.net>
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
prev parent reply other threads:[~2023-02-21 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 3:28 [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores Zhang Rui
2023-02-20 3:28 ` [PATCH V2 1/1] x86/topology: fix erroneous smp_num_siblings on Intel Hybrid platform Zhang Rui
2023-02-20 11:22 ` Peter Zijlstra
2023-02-21 8:34 ` Zhang, Rui
2023-03-13 2:05 ` Zhang, Rui
2023-02-20 10:36 ` [RFC PATCH V2 0/1] x86: cpu topology fix and question on x86_max_cores Peter Zijlstra
2023-02-20 14:40 ` Zhang, Rui
2023-02-20 11:08 ` Peter Zijlstra
2023-02-20 14:33 ` Zhang, Rui
2023-02-20 19:06 ` Peter Zijlstra
2023-02-20 22:52 ` Thomas Gleixner
2023-02-21 8:01 ` Zhang, Rui
2023-02-20 22:49 ` Thomas Gleixner
2023-02-21 8:26 ` Zhang, Rui
2023-03-07 16:10 ` Zhang, Rui
2023-03-08 2:46 ` Brown, Len
2023-02-21 9:00 ` Peter Zijlstra
2023-02-21 10:09 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y/SYS+LiPVKit4PR@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zhang.jia@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox