[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ba3f7a9c-0b59-cbeb-5d46-4236cde2c51f@redhat.com>
Date: Wed, 31 Mar 2021 09:52:30 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>,
Marc Zyngier <maz@...nel.org>,
Huacai Chen <chenhuacai@...nel.org>,
Aleksandar Markovic <aleksandar.qemu.devel@...il.com>,
Paul Mackerras <paulus@...abs.org>
Cc: James Morse <james.morse@....com>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
linux-mips@...r.kernel.org, kvm@...r.kernel.org,
kvm-ppc@...r.kernel.org, linux-kernel@...r.kernel.org,
Ben Gardon <bgardon@...gle.com>
Subject: Re: [PATCH 10/18] KVM: Move x86's MMU notifier memslot walkers to
generic code
On 26/03/21 03:19, Sean Christopherson wrote:
> +#ifdef KVM_ARCH_WANT_NEW_MMU_NOTIFIER_APIS
> + kvm_handle_hva_range(mn, address, address + 1, pte, kvm_set_spte_gfn);
> +#else
> struct kvm *kvm = mmu_notifier_to_kvm(mn);
> int idx;
> trace_kvm_set_spte_hva(address);
>
> idx = srcu_read_lock(&kvm->srcu);
>
> KVM_MMU_LOCK(kvm);
>
> kvm->mmu_notifier_seq++;
>
> if (kvm_set_spte_hva(kvm, address, pte))
> kvm_flush_remote_tlbs(kvm);
>
> KVM_MMU_UNLOCK(kvm);
> srcu_read_unlock(&kvm->srcu, idx);
> +#endif
The kvm->mmu_notifier_seq is missing in the new API side. I guess you
can add an argument to __kvm_handle_hva_range and handle it also in
patch 15 ("KVM: Take mmu_lock when handling MMU notifier iff the hva
hits a memslot").
Paolo
Powered by blists - more mailing lists