[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8cUfeqeCQLORhbr@a4bf019067fa.jf.intel.com>
Date: Tue, 17 Jan 2023 13:34:53 -0800
From: Ashok Raj <ashok.raj@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: Dave Hansen <dave.hansen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
X86-kernel <x86@...nel.org>,
LKML Mailing List <linux-kernel@...r.kernel.org>,
Tony Luck <tony.luck@...el.com>,
Ingo Molnar <mingo@...nel.org>, <alison.schofield@...el.com>,
<reinette.chatre@...el.com>,
Tom Lendacky <thomas.lendacky@....com>,
"Ashok Raj" <ashok.raj@...el.com>
Subject: Re: [PATCH v4 6/6] x86/microcode/intel: Print when early microcode
loading fails
On Tue, Jan 17, 2023 at 10:06:29PM +0100, Borislav Petkov wrote:
> On Tue, Jan 17, 2023 at 12:40:30PM -0800, Ashok Raj wrote:
> > We just agreed to show both failed and success for late-load.
>
> Did you read the part you snipped about getting false/misleading bug reports? I
> doubt it, as usual.
>
> If you all Intel folks want to deal with people asking why is there a warning
> message about microcode not loading successfully, I don't mind forwarding you
> all those messages. I sure ain't going to deal with them.
TBH, there is nothing to hide from a microcode loading failure. If user
sees that a loading failed, it could be maybe due to corrupted files and
its best to know and update to proper file vs running without the latest
microcode file always.
Powered by blists - more mailing lists