mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
	Prarit Bhargava <prarit@redhat.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	sironi@amazon.de
Subject: Re: [PATCH v2] arch/x86: Fix boot_cpu_data.microcode version output
Date: Wed, 01 Aug 2018 18:01:50 +0200	[thread overview]
Message-ID: <84058a7359c55f2af16a85398df85a36@natalenko.name> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F7D38B681@ORSMSX110.amr.corp.intel.com>

Hi.

On 01.08.2018 17:59, Luck, Tony wrote:
>> There's no reliable way to get the old microcode revision which was
>> overwritten during the upgrade. If dmesg gets overwritten you lose, 
>> like
>> in all the other gazillion cases where you lose information due to 
>> that.
> 
> The primary requirement here is that we report the version of the 
> microcode
> in use at the time of a crash. Keeping history of all updates seems to 
> me to
> beyond the scope of the kernel's responsibilities.
> 
> It's not like these updates appear out of the ether. You have to go out 
> and
> grab a new package and install it.  User land can keep track of this 
> much
> more easily than the kernel.

I don't mind doing the right thing at all. It is just to inform you that 
it was found to be useful.

Also, [1].

Thanks ☺.

[1] https://xkcd.com/1172/

-- 
   Oleksandr Natalenko (post-factum)

  reply	other threads:[~2018-08-01 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20180731112739.32338-1-prarit@redhat.com>
2018-08-01  6:38 ` Oleksandr Natalenko
2018-08-01 11:38   ` Prarit Bhargava
2018-08-01 14:16     ` Oleksandr Natalenko
2018-08-01 15:29       ` Borislav Petkov
2018-08-01 15:59         ` Luck, Tony
2018-08-01 16:01           ` Oleksandr Natalenko [this message]
2018-08-01 16:14             ` Boris Petkov
2018-06-01 12:19 [PATCH] x86/MCE: Get microcode revision from cpu_info instead of boot_cpu_data Borislav Petkov
2018-07-31 11:27 ` [PATCH v2] arch/x86: Fix boot_cpu_data.microcode version output Prarit Bhargava
2018-07-31 11:46   ` Sironi, Filippo
2018-07-31 13:00     ` Borislav Petkov
2018-07-31 15:31       ` Sironi, Filippo
2018-08-01 15:43   ` Borislav Petkov
2018-08-01 15:55     ` Prarit Bhargava

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=84058a7359c55f2af16a85398df85a36@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=sironi@amazon.de \
    --cc=tony.luck@intel.com \
    /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
Powered by JetHome