tree 2af7587ccd189b568129b9e2eccebdcb5cd690d3
parent e12091ce7bdd3c82fa392a868d1bdccecee655d5
author Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> 1357641967 +0900
committer Gleb Natapov <gleb@redhat.com> 1358154849 +0200

KVM: Make kvm_mmu_change_mmu_pages() take mmu_lock by itself

No reason to make callers take mmu_lock since we do not need to protect
kvm_mmu_change_mmu_pages() and kvm_mmu_slot_remove_write_access()
together by mmu_lock in kvm_arch_commit_memory_region(): the former
calls kvm_mmu_commit_zap_page() and flushes TLBs by itself.

Note: we do not need to protect kvm->arch.n_requested_mmu_pages by
mmu_lock as can be seen from the fact that it is read locklessly.

Reviewed-by: Marcelo Tosatti <mtosatti@redhat.com>
Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Signed-off-by: Gleb Natapov <gleb@redhat.com>