Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   "Hurwitz, Sherry" <sherry.hurwitz@amd.com>
To:     Rudolf Marek <r.marek@assembler.cz>,
        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
Thread-Topic: [PATCH 1/1] Update AMD cpu microcode for family 15h
Thread-Index: AQHT88wjL5oKc70JtkGw+Ls62le+yaRAWycAgAf+yQCAAhVRgIAGHTOAgAE8h/A=
Date:   Tue, 5 Jun 2018 14:27:27 +0000
Message-ID: <MWHPR1201MB2526CF0F174938EA64156AE98B660@MWHPR1201MB2526.namprd12.prod.outlook.com>
References: <1527213479-121361-1-git-send-email-sherry.hurwitz@amd.com>
 <CA+5PVA7aPRHk=kfxsmPi-qStKEnK_HJ=rTjvtQGO1QbnLb9qBw@mail.gmail.com>
 <CAAaskFAGRUU3APZbsY2w9hW9jbBJfeMbHt8ttg7vXHidp025=g@mail.gmail.com>
 <20180531220503.2jqs3oiqsnw7ye2t@khazad-dum.debian.net>
 <6402a30f-04d3-59d9-92df-5a43e2060f5c@assembler.cz>
In-Reply-To: <6402a30f-04d3-59d9-92df-5a43e2060f5c@assembler.cz>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: amd.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6a548208-5200-482e-4b8b-08d5caf076dc
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2018 14:27:27.6653
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR1201MB0239
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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 n=
ot been given for public publishing.  It might have come from a BIOS update=
 and not a OS microcode load but I don't have the definitive details on tha=
t either.  I will publish whatever is released to me as soon as possible.

Sherry

> -----Original Message-----
> From: Rudolf Marek [mailto:r.marek@assembler.cz]
> Sent: Monday, June 04, 2018 2:27 PM
> To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>; Ivan Ivanov
> <qmastery16@gmail.com>
> Cc: Josh Boyer <jwboyer@kernel.org>; Hurwitz, Sherry
> <sherry.hurwitz@amd.com>; 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
>=20
> Hi Sherry,
>=20
> Any news on this please? It seems we still miss updated microcode for cer=
tain
> fam15h/16h for Linux.
>=20
> Thanks
> Rudolf
>=20
>=20
> 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.
>=20
>=20
>=20
> > 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 t=
o
> 0x0600111f, which will support IBPB?
> >
> > Thanks
> > Rudolf
> >
> >
>=20
> > 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 late=
st
> 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-firmwar
> > e.git/commit/amd-
> ucode/microcode_amd_fam15h.bin?id=3D77101513943ef198e20
> > 50667c87abf19e6cbb1d8