From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Tavis Ormandy <taviso@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Alexander Monakov <amonakov@ispras.ru>
Subject: Re: [PATCH] x86/amd: Work around Erratum 1386 - XSAVES malfunction on context switch
Date: Tue, 7 Mar 2023 20:01:36 +0000 [thread overview]
Message-ID: <ee866b3e-a53b-4c26-0272-20e798c0650d@citrix.com> (raw)
In-Reply-To: <20230307185632.GDZAeI4LwBDUU3/OP9@fat_crate.local>
On 07/03/2023 6:56 pm, Borislav Petkov wrote:
> On Tue, Mar 07, 2023 at 06:22:01PM +0000, Andrew Cooper wrote:
>> 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 ?
> We don't have to clear the feature flag on those systems which have
> a fix.
Sure, but why is that helpful?
XSAVES and XSAVEC are functionally identical on Zen1/2 because these
CPUs don't advertise any supervisor XSAVE states.
It is only Zen3 where XSAVES starts doing more than XSAVEC (and even
then, only after the CET series actually gets merged...)
~Andrew
next prev parent reply other threads:[~2023-03-07 20:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 6:40 x86: AMD Zen2 ymm registers rolling back Tavis Ormandy
2023-02-22 8:33 ` Borislav Petkov
2023-02-22 9:14 ` Borislav Petkov
2023-02-22 9:38 ` Andrew Cooper
2023-02-22 10:09 ` Borislav Petkov
2023-02-22 21:26 ` Tavis Ormandy
2023-02-22 22:17 ` Andrew Cooper
2023-02-22 22:26 ` Borislav Petkov
2023-02-22 22:25 ` Borislav Petkov
2023-02-28 18:47 ` Alexander Monakov
2023-02-28 19:20 ` Borislav Petkov
2023-02-28 19:24 ` Alexander Monakov
2023-02-28 19:25 ` Borislav Petkov
2023-02-28 19:29 ` Alexander Monakov
2023-02-28 19:38 ` Andrew Cooper
2023-02-28 21:45 ` Alexander Monakov
2023-02-28 20:56 ` Borislav Petkov
2023-02-28 21:16 ` Alexander Monakov
2023-03-01 0:23 ` Andrew Cooper
2023-03-01 8:54 ` Borislav Petkov
2023-03-07 16:45 ` Tavis Ormandy
2023-03-07 17:46 ` [PATCH] x86/amd: Work around Erratum 1386 - XSAVES malfunction on context switch Andrew Cooper
2023-03-07 17:50 ` Borislav Petkov
2023-03-07 18:22 ` Andrew Cooper
2023-03-07 18:56 ` Borislav Petkov
2023-03-07 20:01 ` Andrew Cooper [this message]
2023-03-07 20:09 ` Borislav Petkov
2023-03-14 16:01 ` Dave Hansen
2023-03-08 16:23 ` [tip: x86/urgent] x86/CPU/AMD: Disable XSAVES on AMD family 0x17 tip-bot2 for Andrew Cooper
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=ee866b3e-a53b-4c26-0272-20e798c0650d@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=amonakov@ispras.ru \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=taviso@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®