diff options
| author | Sean Christopherson <[email protected]> | 2022-08-31 00:17:04 +0000 |
|---|---|---|
| committer | Sean Christopherson <[email protected]> | 2022-11-30 16:19:43 -0800 |
| commit | 5c8c0b3273822cf982c250a9a19e003e4b315edb (patch) | |
| tree | 8bfbdea0b9458fdc313aa198aef2a9ff87f2d274 | |
| parent | 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5 (diff) | |
KVM: x86: Delete documentation for READ|WRITE in KVM_X86_SET_MSR_FILTER
Delete the paragraph that describes the behavior when both
KVM_MSR_FILTER_READ | KVM_MSR_FILTER_WRITE are set for a range. There is
nothing special about KVM's handling of this combination, whereas
explicitly documenting the combination suggests that there is some magic
behavior the user needs to be aware of.
Signed-off-by: Sean Christopherson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
| -rw-r--r-- | Documentation/virt/kvm/api.rst | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index 5617bc4f899f..373cf425e85c 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -4115,13 +4115,6 @@ flags values for ``struct kvm_msr_filter_range``: a write for a particular MSR should be handled regardless of the default filter action. -``KVM_MSR_FILTER_READ | KVM_MSR_FILTER_WRITE`` - - Filter both read and write accesses to MSRs using the given bitmap. A 0 - in the bitmap indicates that both reads and writes should immediately fail, - while a 1 indicates that reads and writes for a particular MSR are not - filtered by this range. - flags values for ``struct kvm_msr_filter``: ``KVM_MSR_FILTER_DEFAULT_ALLOW`` |