mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
	X86 ML <x86@kernel.org>
Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels
Date: Fri, 10 Jul 2015 12:12:00 -0300	[thread overview]
Message-ID: <20150710151159.GA761@khazad-dum.debian.net> (raw)
In-Reply-To: <20150710101151.GA7538@nazgul.tnic>

On Fri, 10 Jul 2015, Borislav Petkov wrote:
> On Thu, Jul 09, 2015 at 12:03:41PM -0300, Henrique de Moraes Holschuh wrote:
> > Is there any way to notify the user that 'processor microcode updates
> > are not available on this system except through a firmware update' ?
> 
> What for?
> 
> Those microcode patch levels are final and shouldn't be upgraded at all.

Yes, I understand that the operating system is not to attempt to update any
microcode that is listed as 'final'.

However, if that requirement exists because a microcode update applied by
the operating system would interact badly with the current firmware (or
microcode), the user could still get newer microcode (and better features,
errata workarounds, etc) through a full firmware (BIOS/EFI) update.

OTOH, if this is a 'microcode updates newer than the 'final' version exist
only to support changed hardware designs', and thus a board that already
works with 'final' should never need newer microcode, it would be nice to
know that fact.

Anyway, the code does not look like what I would expect if it is the later
case ("updates past 'final' exist only to support for changed hardware
design): it blacklists updates from 'final' to anything else, but it still
allows microcode with a version that is less than 'final' to be updated to
something that is higher than 'final', etc.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2015-07-10 15:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 20:14 Borislav Petkov
2015-07-01 20:14 ` [PATCH 1/2] x86/microcode/amd: Extract current patch level read to a function Borislav Petkov
2015-07-01 20:14 ` [PATCH 2/2] x86/microcode/amd: Do not overwrite final patch levels Borislav Petkov
2015-07-09 15:03 ` [PATCH 0/2] x86/microcode/amd: Do not overwrite specific " Henrique de Moraes Holschuh
2015-07-10 10:11   ` Borislav Petkov
2015-07-10 15:12     ` Henrique de Moraes Holschuh [this message]
2016-03-26 23:31 ` Henrique de Moraes Holschuh
2016-03-27  8:31   ` Borislav Petkov
2016-03-27 12:32     ` Henrique de Moraes Holschuh
2016-03-27 15:47       ` Borislav Petkov
2016-05-02 15:30         ` Borislav Petkov
2016-05-06 12:43           ` Henrique de Moraes Holschuh
2016-05-06 13:23             ` 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=20150710151159.GA761@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®