aboutsummaryrefslogtreecommitdiff
path: root/virt/kvm/pfncache.c
diff options
context:
space:
mode:
authorGravatar Sean Christopherson <seanjc@google.com> 2022-03-25 23:03:48 +0000
committerGravatar Paolo Bonzini <pbonzini@redhat.com> 2022-04-02 05:34:39 -0400
commitf47e5bbbc92f5d234bbab317523c64a65b6ac4e2 (patch)
tree15072e9c822f4ad09c856670244c3c5c753a3c91 /virt/kvm/pfncache.c
parentKVM: SVM: fix panic on out-of-bounds guest IRQ (diff)
downloadlinux-f47e5bbbc92f5d234bbab317523c64a65b6ac4e2.tar.gz
linux-f47e5bbbc92f5d234bbab317523c64a65b6ac4e2.tar.bz2
linux-f47e5bbbc92f5d234bbab317523c64a65b6ac4e2.zip
KVM: x86/mmu: Zap only TDP MMU leafs in zap range and mmu_notifier unmap
Re-introduce zapping only leaf SPTEs in kvm_zap_gfn_range() and kvm_tdp_mmu_unmap_gfn_range(), this time without losing a pending TLB flush when processing multiple roots (including nested TDP shadow roots). Dropping the TLB flush resulted in random crashes when running Hyper-V Server 2019 in a guest with KSM enabled in the host (or any source of mmu_notifier invalidations, KSM is just the easiest to force). This effectively revert commits 873dd122172f8cce329113cfb0dfe3d2344d80c0 and fcb93eb6d09dd302cbef22bd95a5858af75e4156, and thus restores commit cf3e26427c08ad9015956293ab389004ac6a338e, plus this delta on top: bool kvm_tdp_mmu_zap_leafs(struct kvm *kvm, int as_id, gfn_t start, gfn_t end, struct kvm_mmu_page *root; for_each_tdp_mmu_root_yield_safe(kvm, root, as_id) - flush = tdp_mmu_zap_leafs(kvm, root, start, end, can_yield, false); + flush = tdp_mmu_zap_leafs(kvm, root, start, end, can_yield, flush); return flush; } Cc: Ben Gardon <bgardon@google.com> Signed-off-by: Sean Christopherson <seanjc@google.com> Tested-by: Vitaly Kuznetsov <vkuznets@redhat.com> Message-Id: <20220325230348.2587437-1-seanjc@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt/kvm/pfncache.c')
0 files changed, 0 insertions, 0 deletions