diff options
| author |   Raghavendra Rao Ananta <rananta@google.com> | 2023-08-11 04:51:25 +0000 |
|---|---|---|
| committer |   Marc Zyngier <maz@kernel.org> | 2023-08-17 09:40:35 +0100 |
| commit | 3756b6f2bb3a242fef0867b39a23607f5aeca138 (patch) | |
| tree | 78546bcd6ffaa6f9031c2a94076eedec312acfe2 | |
| parent | KVM: arm64: Implement kvm_arch_flush_remote_tlbs_range() (diff) | |
| download | wireguard-linux-3756b6f2bb3a242fef0867b39a23607f5aeca138.tar.xz wireguard-linux-3756b6f2bb3a242fef0867b39a23607f5aeca138.zip | |
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 <rananta@google.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
Reviewed-by: Shaoqin Huang <shahuang@redhat.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20230811045127.3308641-13-rananta@google.com
| -rw-r--r-- | arch/arm64/kvm/mmu.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c index c73cec797519..b16aff3f65f6 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); } /** |