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 17:46:24 +0200 [thread overview]
Message-ID: <b01e8484-17e6-5253-5d83-9d864c66a7f9@assembler.cz> (raw)
In-Reply-To: <MWHPR1201MB2526CF0F174938EA64156AE98B660@MWHPR1201MB2526.namprd12.prod.outlook.com>
Hi Sherry,
Dne 5.6.2018 v 16:27 Hurwitz, Sherry napsal(a):
> Hi Rudolf, I have been investigating the status with the AMD release
> management, but I have not been given approval to publish any other
> microcode. I have been trying to track down why there might be a
> version in the wild that I have not been given for public publishing.
> It might have come from a BIOS update and not a OS microcode load but
Yes exactly. Why this exists? Is there some technical restriction that will prevent
microcode loading just in Linux? I think it would be beneficial to have at least
the IBPB protection in place via microcode updates.
> I don't have the definitive details on that either. I will publish
> whatever is released to me as soon as possible.
Any news on this? The family 15h microcode revision provided for Linux is 0x06001119 but I know that 0x0600111f
exists, which provides the IBPB.
Btw I also think that Family 17h (0x00800F11) Linux microcode update has a same problem.
It does not include IBPB support right? It is included in the "BIOS" only microcode revision 0x08001137.
Thanks,
Rudolf
next prev parent reply other threads:[~2018-09-01 15:54 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 [this message]
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=b01e8484-17e6-5253-5d83-9d864c66a7f9@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®