diff options
| author | Sean Christopherson <seanjc@google.com> | 2024-10-09 21:23:45 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-10-20 13:31:05 +0200 |
| commit | 5a279842441b68727d53b6333d0c3af90dd5a2f8 (patch) | |
| tree | 0dbddcf084a9e75d1711213abdbb3d2648702e4e /arch/x86 | |
| parent | KVM: x86/mmu: Add lockdep assert to enforce safe usage of kvm_unmap_gfn_range() (diff) | |
| download | linux-5a279842441b68727d53b6333d0c3af90dd5a2f8.tar.xz linux-5a279842441b68727d53b6333d0c3af90dd5a2f8.zip | |
KVM: x86: Clean up documentation for KVM_X86_QUIRK_SLOT_ZAP_ALL
Massage the documentation for KVM_X86_QUIRK_SLOT_ZAP_ALL to call out that
it applies to moved memslots as well as deleted memslots, to avoid KVM's
"fast zap" terminology (which has no meaning for userspace), and to reword
the documented targeted zap behavior to specifically say that KVM _may_
zap a subset of all SPTEs. As evidenced by the fix to zap non-leafs SPTEs
with gPTEs, formally documenting KVM's exact internal behavior is risky
and unnecessary.
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-ID: <20241009192345.1148353-4-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/x86')
0 files changed, 0 insertions, 0 deletions