[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210321045619.GB67113@otc-nc-03>
Date: Sat, 20 Mar 2021 21:56:19 -0700
From: "Raj, Ashok" <ashok.raj@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: "Pontes, Otavio" <otavio.pontes@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"Luck, Tony" <tony.luck@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ashok Raj <ashok.raj@...el.com>
Subject: Re: [PATCH 1/1] x86/microcode: Check for offline CPUs before
checking for microcode update
On Sat, Mar 20, 2021 at 03:55:46PM +0100, Borislav Petkov wrote:
[snip]
> > microcode : 0x30
> > microcode : 0xde
> > microcode : 0x30
> > microcode : 0xde
>
> Yeah, I'm looking at that check_online_cpus() thing and wondering why we
> even need that:
>
> 0. So you have CPUs 1 and 3 offline.
> 1. We can update on the subset of cores which are online
> 2. If a core is offline and comes online, we have the hotplug notifier:
>
> cpuhp_setup_state_nocalls(CPUHP_AP_ONLINE_DYN, "x86/microcode:online",
> mc_cpu_online, mc_cpu_down_prep);
>
> which takes care of updating the microcode when that CPU comes online.
>
> So unless your microcode folks don't come back with a real requirement
> why all CPUs must absolutely be online for a late update, then the
> proper fix is to get rid of check_online_cpus() altogether and update
> what's online and the rest will get updated when they come online.
Its true we update them during the online flow, but the core is still
behind compared to other cores. It still participates when it enters SMM,
or when running MCE for instance. Unless its in WAIT_FOR_SIPI state its
best to not leave a core behind when updating microcode.
--
Cheers,
Ashok
[Forgiveness is the attribute of the STRONG - Gandhi]
Powered by blists - more mailing lists