On Thu, Feb 01, 2018 at 10:59:46PM +0100, KarimAllah Ahmed wrote:
> [ Based on a patch from Paolo Bonzini <pbonz...@redhat.com> ]
>
> ... basically doing exactly what we do for VMX:
>
> - Passthrough SPEC_CTRL to guests (if enabled in guest CPUID)
> - Save and restore SPEC_CTRL around VMExit and VMEntry only if the guest
> actually used it.
>
> Cc: Asit Mallick <asit.k.mall...@intel.com>
> Cc: Arjan Van De Ven <arjan.van.de....@intel.com>
> Cc: Dave Hansen <dave.han...@intel.com>
> Cc: Andi Kleen <a...@linux.intel.com>
> Cc: Andrea Arcangeli <aarca...@redhat.com>
> Cc: Linus Torvalds <torva...@linux-foundation.org>
> Cc: Tim Chen <tim.c.c...@linux.intel.com>
> Cc: Thomas Gleixner <t...@linutronix.de>
> Cc: Dan Williams <dan.j.willi...@intel.com>
> Cc: Jun Nakajima <jun.nakaj...@intel.com>
> Cc: Paolo Bonzini <pbonz...@redhat.com>
> Cc: David Woodhouse <d...@amazon.co.uk>
> Cc: Greg KH <gre...@linuxfoundation.org>
> Cc: Andy Lutomirski <l...@kernel.org>
> Cc: Ashok Raj <ashok....@intel.com>
> Signed-off-by: KarimAllah Ahmed <karah...@amazon.de>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.w...@oracle.com>
> + { .index = MSR_IA32_SPEC_CTRL, .always = false },
This .always = [false|true] field keeps throwing me off.
So glad: https://www.spinics.net/lists/kvm/msg161606.html explains it better.
