Subject: Re: AMD EPYC microcode update bug?
To: Gabriel C <nix.or.die@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@alien8.de>
References: <CAEJqkghB0hE0XzDDrFsnet7dPvnBSvaCOz5ahaGSaw-RfjzWLQ@mail.gmail.com>
 <997def1f-c8d6-15e3-3505-2a4a78b072ab@amd.com>
 <CAEJqkggKwp09nZB8E-VrDQH_giUBiJnn23NGFCXZW2X+NOaaBg@mail.gmail.com>
From: Tom Lendacky <thomas.lendacky@amd.com>
Message-ID: <13930998-4e26-d986-f01d-4d9ff4db0a07@amd.com>
Date: Tue, 9 Jan 2018 17:44:08 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAEJqkggKwp09nZB8E-VrDQH_giUBiJnn23NGFCXZW2X+NOaaBg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Jan 2018 23:44:12.5072 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0de8a3f6-ff05-4a31-4f93-08d557bae343
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 3dd8961f-e488-4e60-8e11-a82d994e183d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR12MB1144
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On 1/9/2018 5:06 PM, Gabriel C wrote:
> 2018-01-09 23:47 GMT+01:00 Tom Lendacky <thomas.lendacky@amd.com>:
>> On 1/9/2018 4:28 PM, Gabriel C wrote:
>>> Hello ,
>>>
>>> I'm testing an EPYC system right now with 2 EPYC 7281 16-Core Processors.
>>>
>>> I'm on 4.15.0-rc7 and tested an update to microcode_amd_fam17h.bin.
>>>
>>> First run was made by using the early microcode option with dracut[1]
>>> so loading from a initrd. the driver reported 63 updated CPUs while CPU0
>>> got still old microcode.
>>
>> I'm guessing that memory encryption is enabled, correct?  I've submitted a
>> patch series to perform early initrd decryption for just this problem. I'm
>> incorporating some minor feedback and getting ready to submit the next
>> version.
> 
> Yes is correct I use mem_encrypt=on and SMT on in BIOS.
> 
> Can you give me an link to the patch series ?

Here's the link: https://marc.info/?l=linux-kernel&m=151389377606957&w=2

Thanks,
Tom

> 
>>
>> In the meantime, if you specify mem_encrypt=off on the kernel command line
>> it should show CPU0 updated properly (with mem_encrypt=on and SMT enabled,
>> I believe it really does get updated when the sibling hread is updated -
>> do a rdmsr of 0x0000008b to verify).
>>
> 
> I give that an test in a bit , the box is running now some test for a
> different EPYC issue :)
> 
> ( https://community.amd.com/thread/224000 )
> 
> Regards,
> 
> Gabriel C
>