Commit 614f3629 authored by Huacai Chen's avatar Huacai Chen
Browse files

LoongArch: KVM: Fix build due to API changes 



Commit 8569992d ("KVM: Use gfn instead of hva for
mmu_notifier_retry") replaces mmu_invalidate_retry_hva() usage with
mmu_invalidate_retry_gfn() for X86, LoongArch also need similar changes
to fix build.

Signed-off-by: default avatarHuacai Chen <chenhuacai@loongson.cn>
parent 5056c596

arch/loongarch/kvm/mmu.c

+2 −2
Original line number Diff line number Diff line
@@ -675,7 +675,7 @@ static bool fault_supports_huge_mapping(struct kvm_memory_slot *memslot, 
 *

 * There are several ways to safely use this helper:

 *

 * - Check mmu_invalidate_retry_hva() after grabbing the mapping level, before

 * - Check mmu_invalidate_retry_gfn() after grabbing the mapping level, before

 *   consuming it.  In this case, mmu_lock doesn't need to be held during the

 *   lookup, but it does need to be held while checking the MMU notifier.

 *
@@ -855,7 +855,7 @@ static int kvm_map_page(struct kvm_vcpu *vcpu, unsigned long gpa, bool write) 


	/* Check if an invalidation has taken place since we got pfn */

	spin_lock(&kvm->mmu_lock);

	if (mmu_invalidate_retry_hva(kvm, mmu_seq, hva)) {

	if (mmu_invalidate_retry_gfn(kvm, mmu_seq, gfn)) {

		/*

		 * This can happen when mappings are changed asynchronously, but

		 * also synchronously if a COW is triggered by