[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <940596cc-a440-181a-a72a-36282a26dd0a@citrix.com>
Date: Tue, 7 Mar 2023 18:22:01 +0000
From: Andrew Cooper <andrew.cooper3@...rix.com>
To: Borislav Petkov <bp@...en8.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Tavis Ormandy <taviso@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Alexander Monakov <amonakov@...ras.ru>
Subject: Re: [PATCH] x86/amd: Work around Erratum 1386 - XSAVES malfunction on
context switch
On 07/03/2023 5:50 pm, Borislav Petkov wrote:
> On Tue, Mar 07, 2023 at 05:46:43PM +0000, Andrew Cooper wrote:
>> + * Work around Erratum 1386. The XSAVES instruction malfunctions in
>> + * certain circumstances on Zen1/2 uarch, and not all parts have had
>> + * updated microcode at the time of writing (March 2023).
> Any reason for rushing this and not waiting for me to clarify affected
> models first?
Well yes - more and more reports of impacted systems.
Having the full list of affected models is great and all, but how is it
going to change this patch as a workaround ?
~Andrew
Powered by blists - more mailing lists