public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 14:50:00 +0100	[thread overview]
Message-ID: <1516974600.2801.10.camel@redhat.com> (raw)
In-Reply-To: <20180126115800.bvqrzik2f3hmmiah@pd.tnic>

Borislav Petkov píše v Pá 26. 01. 2018 v 12:58 +0100:
> On Fri, Jan 26, 2018 at 12:45:35PM +0100, Petr Oros wrote:
> > 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.
> 
> Dmesg tells you if the update was applied or not.
> 
> And if you really wanna know the old microcode revision, you can boot
> with "dis_ucode_ldr" and do "grep microcode /proc/cpuinfo".
> 

Ohh, yes, it is easy and fast. Mainly in time when new microcodes are released
frequently and microcode can be early updated from initrd too.

But what in production? Edit boot params, restart server, grep /proc/cpuinfo and
restart again? Why i can not read it just from dmesg?

Thanks,
-Petr

  reply	other threads:[~2018-01-26 13:52 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
2018-01-26 11:58     ` Borislav Petkov
2018-01-26 13:50       ` Petr Oros [this message]
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=1516974600.2801.10.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