[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180130013014.GE21702@localhost.localdomain>
Date: Mon, 29 Jan 2018 23:30:14 -0200
From: Eduardo Habkost <ehabkost@...hat.com>
To: David Dunn <ddunn@...are.com>
Cc: Jim Mattson <jmattson@...gle.com>, Andi Kleen <ak@...ux.intel.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
KarimAllah Ahmed <karahmed@...zon.de>,
"Wilson, Matt" <msw@...zon.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrea Arcangeli <aarcange@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
Ashok Raj <ashok.raj@...el.com>,
Asit Mallick <asit.k.mallick@...el.com>,
Borislav Petkov <bp@...e.de>,
Dan Williams <dan.j.williams@...el.com>,
Dave Hansen <dave.hansen@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"H . Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Janakarajan Natarajan <Janakarajan.Natarajan@....com>,
Joerg Roedel <joro@...tes.org>,
Jun Nakajima <jun.nakajima@...el.com>,
Laura Abbott <labbott@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Radim Krčmář <rkrcmar@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Tom Lendacky <thomas.lendacky@....com>,
"Jorgensen, Bryan" <bryan.jorgensen@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"Dr. David Alan Gilbert" <dgilbert@...hat.com>,
Fred Jacobs <fjacobs@...are.com>,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: [RFC,05/10] x86/speculation: Add basic IBRS support
infrastructure
On Tue, Jan 30, 2018 at 01:20:52AM +0000, David Dunn wrote:
> Eduardo,
>
> This is why it would be good to have a CPUID bit that says:
> "apply SkyLake RSB stuffing." That's preferable to "trust FMS"
> for VMware.
Agreed it would be more useful than "trust FMS". However, I
believe a "no need to apply Skylake RSB stuffing" bit (which I
called "we promise we won't migrate to Skylake" previously) would
allow guests to enable safer behavior by default under older
hypervisors that don't support this bit.
>
> If Intel defines such a feature flag, sets it on SkyLake, and
> Linux uses it... that would be very helpful for VMware.
>
> I won't speak for GCE and AWS. But hopefully they can indicate
> whether it would help them as well.
I agree that having a standard flag on the CPUID space to specify
that would be very helpful.
>
> If Intel cannot define/implement such a flag on SkyLake, then
> maybe the engineers on this email could define a flag in the
> hypervisor specific CPUID space. Linux would need to query
> that flag if it sees CPUID[1].ECX[31] set. That's not as nice
> since it makes detection on bare metal and virtualization
> platforms different, but it better than keying off FMS.
Agreed.
--
Eduardo
Powered by blists - more mailing lists