[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8bI4BBst78qrApD@a4bf019067fa.jf.intel.com>
Date: Tue, 17 Jan 2023 08:12:16 -0800
From: Ashok Raj <ashok.raj@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: Thomas Gleixner <tglx@...utronix.de>, X86-kernel <x86@...nel.org>,
"LKML Mailing List" <linux-kernel@...r.kernel.org>,
Dave Hansen <dave.hansen@...el.com>,
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 Sun, Jan 15, 2023 at 08:05:14PM +0100, Borislav Petkov wrote:
> On Mon, Jan 09, 2023 at 07:35:55AM -0800, Ashok Raj wrote:
> > Currently when early microcode loading fails there is no way for the
> > user to know that the update failed.
>
> Of course there is - there's no early update message in dmesg.
Sorry Boris, didn't comprehend.
Without user making some additional steps to check the revision in the
default location and the current rev reported to find the update failed.
Maybe that's what you meant.
Powered by blists - more mailing lists