Commit b16ff629 authored by Nicolai Stange's avatar Nicolai Stange Committed by Greg Kroah-Hartman
Browse files

x86/KVM/VMX: Don't set l1tf_flush_l1d from vmx_handle_external_intr()

commit 18b57ce2


For VMEXITs caused by external interrupts, vmx_handle_external_intr()
indirectly calls into the interrupt handlers through the host's IDT.

It follows that these interrupts get accounted for in the
kvm_cpu_l1tf_flush_l1d per-cpu flag.

The subsequently executed vmx_l1d_flush() will thus be aware that some
interrupts have happened and conduct a L1d flush anyway.

Setting l1tf_flush_l1d from vmx_handle_external_intr() isn't needed
anymore. Drop it.
Signed-off-by: default avatarNicolai Stange <>
Signed-off-by: default avatarThomas Gleixner <>
Signed-off-by: default avatarGreg Kroah-Hartman <>
parent 3131918d
......@@ -10019,7 +10019,6 @@ static void vmx_handle_external_intr(struct kvm_vcpu *vcpu)
vcpu->arch.l1tf_flush_l1d = true;
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment