[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180222121506.GC27489@pd.tnic>
Date: Thu, 22 Feb 2018 13:15:06 +0100
From: Borislav Petkov <bp@...e.de>
To: "Raj, Ashok" <ashok.raj@...el.com>
Cc: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Tony Luck <tony.luck@...el.com>,
Andi Kleen <andi.kleen@...el.com>,
Tom Lendacky <thomas.lendacky@....com>,
Arjan Van De Ven <arjan.van.de.ven@...el.com>
Subject: Re: [v2 1/3] x86/microcode/intel: Check microcode revision before
updating sibling threads
On Thu, Feb 22, 2018 at 03:55:54AM -0800, Raj, Ashok wrote:
> The current code wasn't trying to enforce checking the loaded microcode revision on a thread
> before attempting to load the microcode. While you comeback from resume, if C0T0 already
> is up, and we loaded the early microcode, then when handling C0T1 there is no need to
> do a wrmsrl to reapply microcode since its already loaded as part of C0T0.
And I'm asking exactly this: is it simply "we don't need to do WRMSR" or
"we should not"?
Because avoiding the WRMSR costs more than simply doing it and letting
the HT thread ignore the supplied microcode.
If it is "we don't need to but there's nothing wrong when we do it" then
we don't need this patch. And I'm pretty sure "nothing wrong when we do
it" would be the answer. Otherwise we have bigger problems.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists