KVM: x86/mmu: Move the misplaced export of kvm_zap_gfn_range()
PATCH 1/1 KVM: x86/mmu: Move the misplaced export of kvm_zap_gfn_range()
Currently, the export of kvm_zap_gfn_range() is misplaced, i.e., it's not placed right after the kvm_zap_gfn_range() function body but after kvm_mmu_zap_collapsible_spte(). Move it to the right place.
No functional change intended.
Signed-off-by Kai Huang <[email protected]>
--- arch/x86/kvm/mmu/mmu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/mmu/mmu.c +1 -1
@@ -6863,6 +6863,7 @@ void kvm_zap_gfn_range(struct kvm *kvm, gfn_t gfn_start, gfn_t gfn_end)write_unlock (&kvm->mmu_lock); } +EXPORT_SYMBOL_FOR_KVM_INTERNAL (kvm_zap_gfn_range); static bool slot_rmap_write_protect(struct kvm *kvm, struct kvm_rmap_head *rmap_head,
@@ -7204,7 +7205,6 @@ static bool kvm_mmu_zap_collapsible_spte(struct kvm *kvm,return need_tlb_flush; } -EXPORT_SYMBOL_FOR_KVM_INTERNAL (kvm_zap_gfn_range);static void kvm_rmap_zap_collapsible_sptes (struct kvm *kvm,const struct kvm_memory_slot *slot)
base-commit: b850841a53c56665c1f623edd429b3fc1578e9a4
Signature · 1 line
2.51.0
Quoted 8 lines · Kai Huang
Currently, the export of
kvm_zap_gfn_range()is misplaced, i.e., it's not placed right after thekvm_zap_gfn_range()function body but afterkvm_mmu_zap_collapsible_spte(). Move it to the right place.No functional change intended.
[...]
Applied to kvm-x86 mmu, thanks!
[1/1] KVM: x86/mmu: Move the misplaced export of kvm_zap_gfn_range()
https://github.com/kvm-x86/linux/commit/6422060aa9c7