From: David Woodhouse <dwmw2@infradead.org>
To: Liran Alon <liran.alon@oracle.com>, dave.hansen@intel.com
Cc: labbott@redhat.com, luto@kernel.org,
Janakarajan.Natarajan@amd.com, bp@suse.de,
torvalds@linux-foundation.org, asit.k.mallick@intel.com,
rkrcmar@redhat.com, karahmed@amazon.de, hpa@zytor.com,
jun.nakajima@intel.com, mingo@redhat.com, x86@kernel.org,
ashok.raj@intel.com, arjan.van.de.ven@intel.com,
tim.c.chen@linux.intel.com, pbonzini@redhat.com,
ak@linux.intel.com, linux-kernel@vger.kernel.org,
peterz@infradead.org, tglx@linutronix.de,
gregkh@linuxfoundation.org, mhiramat@kernel.org,
arjan@linux.intel.com, thomas.lendacky@amd.com,
dan.j.williams@intel.com, joro@8bytes.org, aarcange@redhat.com,
kvm@vger.kernel.org
Subject: Re: [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation
Date: Fri, 26 Jan 2018 08:46:57 +0000 [thread overview]
Message-ID: <1516956417.30244.154.camel@infradead.org> (raw)
In-Reply-To: <7c0b0879-3448-43e4-8380-4708fc787113@default>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Thu, 2018-01-25 at 18:11 -0800, Liran Alon wrote:
>
> P.S:
> It seems to me that all these issues could be resolved completely at
> hardware in future CPUs if BTB/BHB/RSB entries were tagged with
> prediction-mode (or similar metadata). It will be nice if Intel/AMD
> could share if that is the planned long-term solution instead of
> IBRS-all-the-time.
IBRS-all-the-time is tagging with the ring and VMX root/non-root mode,
it seems. That much they could slip into the upcoming generation of
CPUs. And it's supposed to be fast¹; none of the dirty hacks in
microcode that they needed to implement the first-generation IBRS.
But we still need to tag with ASID/VMID and do proper flushing for
those, before we can completely ditch the need to do IBPB at the right
times.
Reading between the lines, I don't think they could add *that* without
stopping the fabs for a year or so while they go back to the drawing
board. But yes, I sincerely hope they *are* planning to do it, and
expose a 'SPECTRE_NO' bit in IA32_ARCH_CAPABILITIES, as soon as is
humanly possible.
¹ Fast enough that we'll want to use it and ALTERNATIVE out the
retpolines.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]
next prev parent reply other threads:[~2018-01-26 8:48 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 2:11 [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation Liran Alon
2018-01-26 2:23 ` Dave Hansen
2018-01-26 9:11 ` David Woodhouse
2018-01-26 17:19 ` Linus Torvalds
2018-01-26 17:27 ` Borislav Petkov
2018-01-26 17:29 ` David Woodhouse
2018-01-26 17:31 ` David Woodhouse
2018-01-26 17:59 ` Andi Kleen
2018-01-26 18:11 ` David Woodhouse
2018-01-26 18:12 ` Arjan van de Ven
2018-01-26 18:26 ` David Woodhouse
2018-01-26 18:28 ` Van De Ven, Arjan
2018-01-26 18:43 ` David Woodhouse
2018-01-26 18:44 ` Van De Ven, Arjan
2018-01-26 18:53 ` David Woodhouse
2018-01-26 19:02 ` Konrad Rzeszutek Wilk
2018-01-26 19:11 ` Hansen, Dave
2018-01-27 13:42 ` Konrad Rzeszutek Wilk
2018-01-27 15:55 ` Dave Hansen
2018-01-26 19:11 ` David Woodhouse
2018-01-26 8:46 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-26 2:50 Liran Alon
2018-01-26 2:55 ` Van De Ven, Arjan
2018-01-23 11:13 Liran Alon
2018-01-25 22:20 ` Dave Hansen
2018-01-20 19:22 [RFC 00/10] Speculation Control feature support KarimAllah Ahmed
2018-01-20 19:23 ` [RFC 09/10] x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation KarimAllah Ahmed
2018-01-21 19:14 ` Andy Lutomirski
2018-01-23 16:12 ` Tom Lendacky
2018-01-23 16:20 ` Woodhouse, David
2018-01-23 22:37 ` Tom Lendacky
2018-01-23 22:49 ` Andi Kleen
2018-01-23 23:14 ` Woodhouse, David
2018-01-23 23:22 ` Andi Kleen
2018-01-24 0:47 ` Tim Chen
2018-01-24 1:00 ` Andy Lutomirski
2018-01-24 1:22 ` David Woodhouse
2018-01-24 1:59 ` Van De Ven, Arjan
2018-01-24 3:25 ` Andy Lutomirski
[not found] ` <CA+55aFxUEPHc7JRQG3zmxEsfmfJOiJa1QqFBKCBNb5Tt5vfiSg@mail.gmail.com>
2018-01-21 20:28 ` David Woodhouse
2018-01-21 21:35 ` Linus Torvalds
2018-01-21 22:00 ` David Woodhouse
2018-01-21 22:27 ` Linus Torvalds
2018-01-22 16:27 ` David Woodhouse
2018-01-23 7:29 ` Ingo Molnar
2018-01-23 7:53 ` Ingo Molnar
2018-01-23 9:27 ` Ingo Molnar
2018-01-23 9:37 ` David Woodhouse
2018-01-23 15:01 ` Dave Hansen
2018-01-23 9:30 ` David Woodhouse
2018-01-23 10:15 ` Ingo Molnar
2018-01-23 10:27 ` David Woodhouse
2018-01-23 10:44 ` Ingo Molnar
2018-01-23 10:23 ` Ingo Molnar
2018-02-04 18:43 ` Thomas Gleixner
2018-02-04 20:22 ` David Woodhouse
2018-02-06 9:14 ` David Woodhouse
2018-01-23 20:16 ` Pavel Machek
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=1516956417.30244.154.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=Janakarajan.Natarajan@amd.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan.van.de.ven@intel.com \
--cc=arjan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=jun.nakajima@intel.com \
--cc=karahmed@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--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).