mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@assembler.cz>
To: "Hurwitz, Sherry" <sherry.hurwitz@amd.com>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Ivan Ivanov <qmastery16@gmail.com>
Cc: Josh Boyer <jwboyer@kernel.org>,
	Linux Firmware <linux-firmware@kernel.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
	"Grimm, Jon" <Jon.Grimm@amd.com>
Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h
Date: Sat, 1 Sep 2018 19:09:47 +0200	[thread overview]
Message-ID: <05d222ba-768f-5095-cc7a-f48fc8b3154f@assembler.cz> (raw)
In-Reply-To: <b01e8484-17e6-5253-5d83-9d864c66a7f9@assembler.cz>

Hi again,

Here is a short summary of what is missing in the microcode containers [1] [2]. I only included AMD family 15h and 17h.
Similar could be done for Intel CPUs. 

I do believe having a latest microcode is a vital for the userspace security because it provides
IBPB barrier.

Family 15h [1] container parsed with [4] (with some lines omitted)

-- Processor Signature:       : 0x00600f20
-- Processor Revision ID:     : 0x00006020

-- Processor Signature:       : 0x00610f01
-- Processor Revision ID:     : 0x00006101

-- Processor Signature:       : 0x00600f12
-- Processor Revision ID:     : 0x00006012

Contains following microcodes:

| # | eqrev| urev     |    date    | latest|
| 1 | 6012 | 0600063E | 2018/02/07 |  yes  |
| 2 | 6020 | 06000852 | 2018/02/06 |  yes  |
| 3 | 6101 | 06001119 | 2012/07/13 |  no   |

Note the #3 is what I have been complaining about.

Family 17h [2] parsed with [4]

The container seems to include the equivalent versions for various CPUs (not even a family17h) but only a microcode for a "Naples/EPYC" chips.

Container Processor Signature Table: 
-- Processor Signature:       : 0x00600f20 (not even a fam17h)
-- Processor Revision ID:     : 0x00006020

-- Processor Signature:       : 0x00610f01 (not even a fam17h)
-- Processor Revision ID:     : 0x00006101

-- Processor Signature:       : 0x00700f01 (not even a fam17h)
-- Processor Revision ID:     : 0x00007001

-- Processor Signature:       : 0x00800f12 (update is OK)
-- Processor Revision ID:     : 0x00008012

-- Processor Signature:       : 0x00800f11 (update is missing!)
-- Processor Revision ID:     : 0x00008011

-- Processor Signature:       : 0x00600f12 (not even a fam17h)
-- Processor Revision ID:     : 0x00006012

-- Processor Signature:       : 0x00800f13 (future CPU?)
-- Processor Revision ID:     : 0x00008013

-- Processor Signature:       : 0x00800f00 (perhaps ES?)
-- Processor Revision ID:     : 0x00008000

Microcode Type:               : 0x00000001
Microcode Size:               : 0x00000c80
Date                          : 2018/02/09
Patch ID                      : 0x08001227
Patch Data ID                 : 0x00008004

| # | eqrev| urev     |    date    | latest|
| 1 | 8004 | 08001227 | 2018/02/09 | yes   |

It misses microcode update for 00800F11 - latest known should be 2018/02/14 and for other CPUs like Pinacle Ridge 00800F82 - latest known should be 2018/02/12
Or Ryzen mobile 00810F10 etc...

Thanks
Rudolf

Resources used to construct this tables:

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd-ucode/microcode_amd_fam15h.bin
[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amd-ucode/microcode_amd_fam17h.bin
[3] http://users.atw.hu/instlatx64/
[4] https://github.com/ddcc/microparse


      reply	other threads:[~2018-09-01 17:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  1:57 Sherry Hurwitz
2018-05-25 12:10 ` Josh Boyer
2018-05-30 14:16   ` Ivan Ivanov
2018-05-31 22:05     ` Henrique de Moraes Holschuh
2018-06-04 19:27       ` Rudolf Marek
2018-06-05 14:27         ` Hurwitz, Sherry
2018-06-05 17:55           ` Rudolf Marek
2018-09-01 15:46           ` Rudolf Marek
2018-09-01 17:09             ` Rudolf Marek [this message]

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=05d222ba-768f-5095-cc7a-f48fc8b3154f@assembler.cz \
    --to=r.marek@assembler.cz \
    --cc=Jon.Grimm@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=hmh@hmh.eng.br \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qmastery16@gmail.com \
    --cc=sherry.hurwitz@amd.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

all inboxes | Powered by JetHome®