mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudolf Marek <r.marek@assembler.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Ivan Ivanov <qmastery16@gmail.com>
Cc: Josh Boyer <jwboyer@kernel.org>,
	Sherry Hurwitz <sherry.hurwitz@amd.com>,
	Linux Firmware <linux-firmware@kernel.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	suravee.suthikulpanit@amd.com,
	Tom Lendacky <thomas.lendacky@amd.com>,
	Jon Grimm <jon.grimm@amd.com>
Subject: Re: [PATCH 1/1] Update AMD cpu microcode for family 15h
Date: Mon, 4 Jun 2018 21:27:07 +0200	[thread overview]
Message-ID: <6402a30f-04d3-59d9-92df-5a43e2060f5c@assembler.cz> (raw)
In-Reply-To: <20180531220503.2jqs3oiqsnw7ye2t@khazad-dum.debian.net>

Hi Sherry,

Any news on this please? It seems we still miss updated microcode for certain fam15h/16h for Linux.

Thanks
Rudolf


Dne 1.6.2018 v 00:05 Henrique de Moraes Holschuh napsal(a):
> On Wed, 30 May 2018, Ivan Ivanov wrote:
>> This is still not addressing the outdated 15h microcode version issue
>> that Rudolf Marek has pointed out. Also, we still hope to see an
>> updated microcode for 16h architecture as well - it has not received
>> any updates for two years already
> 
> True, but now at least it won't regress old boxes anymore, so we can
> ship it in the stable branches of the distros with less restrictions.
> 
> It would be really good to be able to actually mitigate spectre v2/v4 on
> most AMD systems, though.  And current experience shows this is only
> going to happen if we can have the required microcode update also going
> through the operating system update channels.



> Dne 24.5.2018 v 16:48 Hurwitz, Sherry napsal(a):
>> Thank you for pointing this out.  Let me investigate and send out an updated fam15h container.
> 
> Thanks I have seen the patch. However it still contains "old" microcode from 2012, patch level
> 0x06001119. Do you plan to update it to 0x0600111f, which will support IBPB?
> 
> Thanks
> Rudolf
> 
> 

> I noticed in commit [1], that 0x00610f01 microcode is removed completely. It has only entry in the equivalence table,
> but the actual microcode is gone. As this update fixes important errata (and it was latest supported microcode officially released), what is the reason behind that?
> 
> Maybe it is a mistake? Or new microcode will be provided? I seen in the wild one with patch level 0x0600111f, but it does not
> seem to be available?
> 
> Please can someone throw some light on that? 
> 
> Many thanks
> Rudolf
> 
> 
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amd-ucode/microcode_amd_fam15h.bin?id=77101513943ef198e2050667c87abf19e6cbb1d8

  reply	other threads:[~2018-06-04 19:35 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 [this message]
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

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=6402a30f-04d3-59d9-92df-5a43e2060f5c@assembler.cz \
    --to=r.marek@assembler.cz \
    --cc=hmh@hmh.eng.br \
    --cc=jon.grimm@amd.com \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qmastery16@gmail.com \
    --cc=sherry.hurwitz@amd.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=thomas.lendacky@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®