[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1806152057020.1582@nanos.tec.linutronix.de>
Date: Fri, 15 Jun 2018 20:57:40 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Tom Lendacky <thomas.lendacky@....com>
cc: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org, x86@...nel.org,
andrew.cooper3@...rix.com, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...e.de>,
David Woodhouse <dwmw@...zon.co.uk>,
Kees Cook <keescook@...omium.org>,
KarimAllah Ahmed <karahmed@...zon.de>
Subject: Re: [PATCH v1 3/3] x86/bugs: Switch the selection of mitigation from
CPU vendor to CPU features
On Tue, 12 Jun 2018, Tom Lendacky wrote:
> On 6/11/2018 9:01 AM, Konrad Rzeszutek Wilk wrote:
> >> I think you will have to keep the case statements and explicitly check for
> >> X86_FEATURE_AMD_SSBD before using SPEC_CTRL.
> >
> > .. we could or alternatively add an extra check for X86_FEATURE_AMD_SSBD ?
>
> Whichever you feel is best, so long as we only use SPEC_CTRL for SSBD on
> AMD when X86_FEATURE_AMD_SSBD is present.
Is there anyone working on a fix or has this been forgotten?
Thanks,
tglx
Powered by blists - more mailing lists