Skip to content

Commit ce2f72e

Browse files
committed
KVM: x86: document limitations of MSR filtering
MSR filtering requires an exit to userspace that is hard to implement and would be very slow in the case of nested VMX vmexit and vmentry MSR accesses. Document the limitation. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
1 parent ac8d6ca commit ce2f72e

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

Documentation/virt/kvm/api.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4081,6 +4081,11 @@ x2APIC MSRs are always allowed, independent of the ``default_allow`` setting,
40814081
and their behavior depends on the ``X2APIC_ENABLE`` bit of the APIC base
40824082
register.
40834083

4084+
.. warning::
4085+
MSR accesses coming from nested vmentry/vmexit are not filtered.
4086+
This includes both writes to individual VMCS fields and reads/writes
4087+
through the MSR lists pointed to by the VMCS.
4088+
40844089
If a bit is within one of the defined ranges, read and write accesses are
40854090
guarded by the bitmap's value for the MSR index if the kind of access
40864091
is included in the ``struct kvm_msr_filter_range`` flags. If no range

0 commit comments

Comments
 (0)