From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: stable@vger.kernel.org, Andrew Cooper <andrew.cooper3@citrix.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH 4.19] x86/CPU/AMD: Fix disabling XSAVES on AMD family 0x17 due to erratum
Date: Fri, 26 Jan 2024 17:17:28 -0800 [thread overview]
Message-ID: <2024012618-daredevil-envious-342a@gregkh> (raw)
In-Reply-To: <d4d6dd5ccb846f128740685ecaeed4f0e9ad13fe.1706205932.git.maciej.szmigiero@oracle.com>
On Thu, Jan 25, 2024 at 07:06:54PM +0100, Maciej S. Szmigiero wrote:
> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>
> The stable kernel version backport of the patch disabling XSAVES on AMD
> Zen family 0x17 applied this change to the wrong function (init_amd_k6()),
> one which isn't called for Zen CPUs.
>
> Move the erratum to the init_amd_zn() function instead.
>
> Add an explicit family 0x17 check to the erratum so nothing will break if
> someone naively makes this kernel version call init_amd_zn() also for
> family 0x19 in the future (as the current upstream code does).
>
> Fixes: f028a7db9824 ("x86/CPU/AMD: Disable XSAVES on AMD family 0x17")
> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
> ---
> arch/x86/kernel/cpu/amd.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
Both fixes now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-01-27 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 18:06 [PATCH 4.19] x86/CPU/AMD: Fix disabling XSAVES on AMD family 0x17 due to erratum Maciej S. Szmigiero
2024-01-27 1:17 ` Greg Kroah-Hartman [this message]
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=2024012618-daredevil-envious-342a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=mail@maciej.szmigiero.name \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.