From: Petr Oros <poros@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision during early update
Date: Fri, 26 Jan 2018 12:45:35 +0100 [thread overview]
Message-ID: <1516967135.2801.1.camel@redhat.com> (raw)
In-Reply-To: <20180126104109.slxxoq4vkqytqjxd@pd.tnic>
Borislav Petkov píše v Pá 26. 01. 2018 v 11:41 +0100:
> On Fri, Jan 26, 2018 at 11:34:50AM +0100, Petr Oros wrote:
> > When kernel do early microcode update, code printing only
> > new microcode version. But in this case we no have chance
> > to check which version was in cpu from BIOS vendor.
>
> And we need that because?
>
During time of facing the Spectre vulnerability and the requirement of handling
different microcode updates, it has shown, that it would be useful to have
additional information which microcode version was in BIOS, if the early-update
routine will apply an update.
next prev parent reply other threads:[~2018-01-26 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 10:34 [PATCH] x86/microcode/intel: print previous microcode revision during early update Petr Oros
2018-01-26 10:41 ` Borislav Petkov
2018-01-26 11:45 ` Petr Oros [this message]
2018-01-26 11:58 ` Borislav Petkov
2018-01-26 13:50 ` Petr Oros
2018-01-26 14:49 ` Borislav Petkov
2018-02-01 18:40 ` Petr Oros
2018-02-07 14:02 ` Stanislav Kozina
2018-02-07 15:21 ` Borislav Petkov
2018-02-07 20:05 ` Stanislav Kozina
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=1516967135.2801.1.camel@redhat.com \
--to=poros@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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