Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 5 Jul 2023 10:35:28 +1000 | Subject | Re: [RESEND PATCH v5 09/11] KVM: arm64: Flush only the memslot after write-protect | From | Gavin Shan <> |
| |
On 6/22/23 03:50, Raghavendra Rao Ananta wrote: > 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> > --- > arch/arm64/kvm/mmu.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >
Reviewed-by: Gavin Shan <gshan@redhat.com>
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c > index c3ec2141c3284..94f10e670c100 100644 > --- a/arch/arm64/kvm/mmu.c > +++ b/arch/arm64/kvm/mmu.c > @@ -992,7 +992,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); > } > > /**
| ![\](/images/icornerr.gif) |