From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bpetkov@suse.de>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH 1/2] x86/bugs: Update when to check for the LS_CFG SSBD mitigation
Date: Tue, 3 Jul 2018 10:12:03 -0400 [thread overview]
Message-ID: <20180703141203.GJ8404@char.us.oracle.com> (raw)
In-Reply-To: <20180702213553.29202.21089.stgit@tlendack-t1.amdoffice.net>
On Mon, Jul 02, 2018 at 04:35:53PM -0500, Tom Lendacky wrote:
> If either the X86_FEATURE_AMD_SSBD or X86_FEATURE_VIRT_SSBD features are
> present, then there is no need to perform the check for the LS_CFG SSBD
> mitigation support.
>
> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
> arch/x86/kernel/cpu/amd.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> index 082d787..38915fb 100644
> --- a/arch/x86/kernel/cpu/amd.c
> +++ b/arch/x86/kernel/cpu/amd.c
> @@ -543,7 +543,9 @@ static void bsp_init_amd(struct cpuinfo_x86 *c)
> nodes_per_socket = ((value >> 3) & 7) + 1;
> }
>
> - if (c->x86 >= 0x15 && c->x86 <= 0x17) {
> + if (!boot_cpu_has(X86_FEATURE_AMD_SSBD) &&
> + !boot_cpu_has(X86_FEATURE_VIRT_SSBD) &&
> + c->x86 >= 0x15 && c->x86 <= 0x17) {
> unsigned int bit;
>
> switch (c->x86) {
>
next prev parent reply other threads:[~2018-07-03 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:35 [PATCH 0/2] x86/bugs: Updates to SSBD support on AMD Tom Lendacky
2018-07-02 21:35 ` [PATCH 1/2] x86/bugs: Update when to check for the LS_CFG SSBD mitigation Tom Lendacky
2018-07-03 8:33 ` [tip:x86/pti] " tip-bot for Tom Lendacky
2018-07-03 14:12 ` Konrad Rzeszutek Wilk [this message]
2018-07-02 21:36 ` [PATCH 2/2] x86/bugs: Fix the AMD SSBD usage of the SPEC_CTRL MSR Tom Lendacky
2018-07-03 8:34 ` [tip:x86/pti] " tip-bot for Tom Lendacky
2018-07-03 14:12 ` [PATCH 2/2] " Konrad Rzeszutek Wilk
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=20180703141203.GJ8404@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=bpetkov@suse.de \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).