diff options
| author |   Waiman Long <longman@redhat.com> | 2019-08-26 15:30:23 -0400 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2019-09-27 18:04:18 +0200 |
| commit | 19a36d329f5b1e5d3d06f7093de992693d0fdee6 (patch) | |
| tree | 2a8e9b48dac78563871a5676b6b3a0e4babf0b56 /tools/testing/selftests/kvm | |
| parent | selftests: kvm: add test for dirty logging inside nested guests (diff) | |
| download | linux-dev-19a36d329f5b1e5d3d06f7093de992693d0fdee6.tar.xz linux-dev-19a36d329f5b1e5d3d06f7093de992693d0fdee6.zip | |
KVM: VMX: Set VMENTER_L1D_FLUSH_NOT_REQUIRED if !X86_BUG_L1TF
The l1tf_vmx_mitigation is only set to VMENTER_L1D_FLUSH_NOT_REQUIRED
when the ARCH_CAPABILITIES MSR indicates that L1D flush is not required.
However, if the CPU is not affected by L1TF, l1tf_vmx_mitigation will
still be set to VMENTER_L1D_FLUSH_AUTO. This is certainly not the best
option for a !X86_BUG_L1TF CPU.
So force l1tf_vmx_mitigation to VMENTER_L1D_FLUSH_NOT_REQUIRED to make it
more explicit in case users are checking the vmentry_l1d_flush parameter.
Signed-off-by: Waiman Long <longman@redhat.com>
[Patch rewritten accoring to Borislav Petkov's suggestion. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/testing/selftests/kvm')
0 files changed, 0 insertions, 0 deletions