x86/spectre_v2: Don't check microcode versions when running under hypervisors
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mon, 26 Feb 2018 14:35:01 +0000 (09:35 -0500)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 8 Mar 2018 09:13:02 +0000 (10:13 +0100)
commit36268223c1e9981d6cfc33aff8520b3bde4b8114
tree18cae517b606794c28c39d0446b55c99b9e80612
parent076ca272a14cea558b1092ec85cea08510283f2a
x86/spectre_v2: Don't check microcode versions when running under hypervisors

As:

 1) It's known that hypervisors lie about the environment anyhow (host
    mismatch)

 2) Even if the hypervisor (Xen, KVM, VMWare, etc) provided a valid
    "correct" value, it all gets to be very murky when migration happens
    (do you provide the "new" microcode of the machine?).

And in reality the cloud vendors are the ones that should make sure that
the microcode that is running is correct and we should just sing lalalala
and trust them.

Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Cc: Wanpeng Li <kernellwp@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Cc: Krčmář <rkrcmar@redhat.com>
Cc: Borislav Petkov <bp@alien8.de>
CC: "H. Peter Anvin" <hpa@zytor.com>
CC: stable@vger.kernel.org
Link: https://lkml.kernel.org/r/20180226213019.GE9497@char.us.oracle.com
arch/x86/kernel/cpu/intel.c