summaryrefslogtreecommitdiffstats
path: root/Documentation/i2c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2019-02-20 09:40:40 +0100
committerThomas Gleixner <tglx@linutronix.de>2019-03-06 21:52:15 +0100
commit22dd8365088b6403630b82423cf906491859b65e (patch)
tree117ad21ac265302596d4a11c35625312f2c25c0a /Documentation/i2c
parent8a4b06d391b0a42a373808979b5028f5c84d9c6a (diff)
downloadlinux-stable-22dd8365088b6403630b82423cf906491859b65e.tar.gz
linux-stable-22dd8365088b6403630b82423cf906491859b65e.tar.bz2
linux-stable-22dd8365088b6403630b82423cf906491859b65e.zip
x86/speculation/mds: Add mitigation mode VMWERV
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>
Diffstat (limited to 'Documentation/i2c')
0 files changed, 0 insertions, 0 deletions