From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-edac@vger.kernel.org,
Filippo Sironi <sironi@amazon.de>
Subject: Re: [PATCH] x86/MCE: Fix CPU microcode version output
Date: Tue, 3 Jul 2018 23:43:00 +0200 [thread overview]
Message-ID: <20180703214300.GA15087@zn.tnic> (raw)
In-Reply-To: <20180703165849.GA17773@agluck-desk>
On Tue, Jul 03, 2018 at 09:58:49AM -0700, Luck, Tony wrote:
> On Tue, Jul 03, 2018 at 12:48:44PM -0400, Prarit Bhargava wrote:
> > On systems where a runtime microcode update has occurred the
> > microcode version is wrong because boot_cpu_data.microcode is
> > not updated during runtime.
> >
> > Use the per-CPU microcode version in the MCE message.
>
> Other option would be to fix the microcode update code to make
> sure that boot_cpu_data.microcode is right.
Yes, I already requested that:
https://lkml.kernel.org/r/1527852626-7258-1-git-send-email-sironi@amazon.de
Looks like Filippo has a patch already. CCed.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-07-03 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:48 [PATCH] x86/MCE: Fix CPU microcode version output Prarit Bhargava
2018-07-03 16:58 ` Luck, Tony
2018-07-03 20:08 ` Prarit Bhargava
2018-07-03 21:43 ` Borislav Petkov [this message]
2018-07-30 15:23 ` Prarit Bhargava
2018-07-30 16:16 ` Borislav Petkov
2018-07-31 7:43 ` Sironi, Filippo
2018-07-31 9:04 ` Borislav Petkov
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=20180703214300.GA15087@zn.tnic \
--to=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=sironi@amazon.de \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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