diff options
author | Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp> | 2013-03-21 19:33:43 +0900 |
---|---|---|
committer | Marcelo Tosatti <mtosatti@redhat.com> | 2013-03-21 19:44:56 -0300 |
commit | 7ddca7e43c8f28f9419da81a0e7730b66aa60fe9 (patch) | |
tree | b1cc5ddac9aa3dae6510309f6c49f8b48e5ab744 /arch/x86/kvm/mmu.h | |
parent | 2ae33b389601b86a3d0cfe2d09f5e3189d5322fd (diff) | |
download | talos-obmc-linux-7ddca7e43c8f28f9419da81a0e7730b66aa60fe9.tar.gz talos-obmc-linux-7ddca7e43c8f28f9419da81a0e7730b66aa60fe9.zip |
KVM: MMU: Move kvm_mmu_free_some_pages() into kvm_mmu_alloc_page()
What this function is doing is to ensure that the number of shadow pages
does not exceed the maximum limit stored in n_max_mmu_pages: so this is
placed at every code path that can reach kvm_mmu_alloc_page().
Although it might have some sense to spread this function in each such
code path when it could be called before taking mmu_lock, the rule was
changed not to do so.
Taking this background into account, this patch moves it into
kvm_mmu_alloc_page() and simplifies the code.
Note: the unlikely hint in kvm_mmu_free_some_pages() guarantees that the
overhead of this function is almost zero except when we actually need to
allocate some shadow pages, so we do not need to care about calling it
multiple times in one path by doing kvm_mmu_get_page() a few times.
Signed-off-by: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'arch/x86/kvm/mmu.h')
0 files changed, 0 insertions, 0 deletions