aboutsummaryrefslogtreecommitdiff
path: root/arch/x86/kernel/cpu/microcode/core.c
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <[email protected]>2018-02-26 09:35:01 -0500
committerThomas Gleixner <[email protected]>2018-03-08 10:13:02 +0100
commit36268223c1e9981d6cfc33aff8520b3bde4b8114 (patch)
tree18cae517b606794c28c39d0446b55c99b9e80612 /arch/x86/kernel/cpu/microcode/core.c
parent076ca272a14cea558b1092ec85cea08510283f2a (diff)
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 <[email protected]> Signed-off-by: Thomas Gleixner <[email protected]> Reviewed-by: Paolo Bonzini <[email protected]> Cc: Wanpeng Li <[email protected]> Cc: kvm <[email protected]> Cc: Krčmář <[email protected]> Cc: Borislav Petkov <[email protected]> CC: "H. Peter Anvin" <[email protected]> CC: [email protected] Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'arch/x86/kernel/cpu/microcode/core.c')
0 files changed, 0 insertions, 0 deletions