From: Raghavendra Rao Ananta Date: Fri, 11 Aug 2023 04:51:25 +0000 (+0000) Subject: KVM: arm64: Flush only the memslot after write-protect X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=3756b6f2bb3a242fef0867b39a23607f5aeca138;p=linux.git KVM: arm64: Flush only the memslot after write-protect After write-protecting the region, currently KVM invalidates the entire TLB entries using kvm_flush_remote_tlbs(). Instead, scope the invalidation only to the targeted memslot. If supported, the architecture would use the range-based TLBI instructions to flush the memslot or else fallback to flushing all of the TLBs. Signed-off-by: Raghavendra Rao Ananta Reviewed-by: Gavin Shan Reviewed-by: Shaoqin Huang Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20230811045127.3308641-13-rananta@google.com --- diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c index c73cec7975192..b16aff3f65f68 100644 --- a/arch/arm64/kvm/mmu.c +++ b/arch/arm64/kvm/mmu.c @@ -1083,7 +1083,7 @@ static void kvm_mmu_wp_memory_region(struct kvm *kvm, int slot) write_lock(&kvm->mmu_lock); stage2_wp_range(&kvm->arch.mmu, start, end); write_unlock(&kvm->mmu_lock); - kvm_flush_remote_tlbs(kvm); + kvm_flush_remote_tlbs_memslot(kvm, memslot); } /**