From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Boris Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@redhat.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH v2] x86/speculation: Add support for STIBP always-on preferred mode
Date: Wed, 12 Dec 2018 15:01:50 +0000 [thread overview]
Message-ID: <5b183bfd-8ef7-2e83-3b2e-c2d889f56b38@amd.com> (raw)
In-Reply-To: <8B17355F-0AE0-4E3A-BFF5-120AB739DB8C@alien8.de>
On 12/12/2018 08:32 AM, Boris Petkov wrote:
> On December 12, 2018 3:04:35 PM GMT+01:00, "Lendacky, Thomas" <Thomas.Lendacky@amd.com> wrote:
>> Not sure I completely follow. Are you saying to do what I did in my
>> first patch or something different from that yet?
>
> I'm saying that STIBP_ALWAYS_ON should be implemented the same way like IBRS_ENHANCED is and there's no need for a static bool. AFAICT.
>
> Or am I missing something?
Ok, I think you're saying to do what my first patch did or something very
close to that. Which is to just set always-on mode if STIBP protection is
requested and the STIBP_ALWAYS_ON CPUID bit is set (even if the equivalent
"=on" is supplied on the command line?). That would mean having the new
mode and new string(s).
If that's not what you're saying, then maybe I just need more coffee this
morning :)
Thanks,
Tom
>
next prev parent reply other threads:[~2018-12-12 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 22:46 [PATCH v2] x86/speculation: Add support for STIBP always-on preferred mode Lendacky, Thomas
2018-12-12 0:05 ` Borislav Petkov
2018-12-12 3:37 ` Thomas Gleixner
2018-12-12 9:59 ` Borislav Petkov
2018-12-12 14:04 ` Lendacky, Thomas
2018-12-12 14:32 ` Boris Petkov
2018-12-12 15:01 ` Lendacky, Thomas [this message]
2018-12-12 14:03 ` Lendacky, Thomas
2018-12-12 14:23 ` Thomas Gleixner
2018-12-12 15:04 ` Lendacky, Thomas
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=5b183bfd-8ef7-2e83-3b2e-c2d889f56b38@amd.com \
--to=thomas.lendacky@amd.com \
--cc=aarcange@redhat.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=jkosina@suse.cz \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.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