diff options
author | Sean Christopherson <[email protected]> | 2023-07-28 18:35:19 -0700 |
---|---|---|
committer | Paolo Bonzini <[email protected]> | 2023-08-31 13:49:00 -0400 |
commit | eeb87272a364311dbfe1b10dd896c3e09a02cd03 (patch) | |
tree | f902d27a2e9b5c869939e7e53748b06bc38a118d /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | db0d70e61082a71e32147733ac082030cdbff0af (diff) |
KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change
Call kvm_mmu_zap_all_fast() directly when flushing a memslot instead of
bouncing through the page-track mechanism. KVM (unfortunately) needs to
zap and flush all page tables on memslot DELETE/MOVE irrespective of
whether KVM is shadowing guest page tables.
This will allow changing KVM to register a page-track notifier on the
first shadow root allocation, and will also allow deleting the misguided
kvm_page_track_flush_slot() hook itself once KVM-GT also moves to a
different method for reacting to memslot changes.
No functional change intended.
Cc: Yan Zhao <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Reviewed-by: Yan Zhao <[email protected]>
Tested-by: Yongwei Ma <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Sean Christopherson <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions