diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2019-02-20 09:40:40 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-14 19:17:57 +0200 |
commit | c50e81fe8a1350f3fb8f355683ed1e6abf368b92 (patch) | |
tree | 196e636899acafbb7da9d83ea23cff58f59f7537 /scripts/checkincludes.pl | |
parent | 8230c2028dce0aa3618524fd69e89bb6084789e6 (diff) | |
download | linux-stable-c50e81fe8a1350f3fb8f355683ed1e6abf368b92.tar.gz linux-stable-c50e81fe8a1350f3fb8f355683ed1e6abf368b92.tar.bz2 linux-stable-c50e81fe8a1350f3fb8f355683ed1e6abf368b92.zip |
x86/speculation/mds: Add mitigation mode VMWERV
commit 22dd8365088b6403630b82423cf906491859b65e upstream
In virtualized environments it can happen that the host has the microcode
update which utilizes the VERW instruction to clear CPU buffers, but the
hypervisor is not yet updated to expose the X86_FEATURE_MD_CLEAR CPUID bit
to guests.
Introduce an internal mitigation mode VMWERV which enables the invocation
of the CPU buffer clearing even if X86_FEATURE_MD_CLEAR is not set. If the
system has no updated microcode this results in a pointless execution of
the VERW instruction wasting a few CPU cycles. If the microcode is updated,
but not exposed to a guest then the CPU buffers will be cleared.
That said: Virtual Machines Will Eventually Receive Vaccine
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jon Masters <jcm@redhat.com>
Tested-by: Jon Masters <jcm@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/checkincludes.pl')
0 files changed, 0 insertions, 0 deletions