Searched hist:b3ae2096974b12c3af2ad1a4e7716b084949867f (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/powerpc/kvm/ |
| H A D | book3s_64_mmu_hv.c | diff b3ae2096974b12c3af2ad1a4e7716b084949867f Mon Jul 02 03:56:33 CDT 2012 Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> KVM: Introduce kvm_unmap_hva_range() for kvm_mmu_notifier_invalidate_range_start()
When we tested KVM under memory pressure, with THP enabled on the host,
we noticed that MMU notifier took a long time to invalidate huge pages.
Since the invalidation was done with mmu_lock held, it not only wasted
the CPU but also made the host harder to respond.
This patch mitigates this by using kvm_handle_hva_range().
Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | kvm_host.h | diff b3ae2096974b12c3af2ad1a4e7716b084949867f Mon Jul 02 03:56:33 CDT 2012 Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> KVM: Introduce kvm_unmap_hva_range() for kvm_mmu_notifier_invalidate_range_start()
When we tested KVM under memory pressure, with THP enabled on the host,
we noticed that MMU notifier took a long time to invalidate huge pages.
Since the invalidation was done with mmu_lock held, it not only wasted
the CPU but also made the host harder to respond.
This patch mitigates this by using kvm_handle_hva_range().
Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | kvm_host.h | diff b3ae2096974b12c3af2ad1a4e7716b084949867f Mon Jul 02 03:56:33 CDT 2012 Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> KVM: Introduce kvm_unmap_hva_range() for kvm_mmu_notifier_invalidate_range_start()
When we tested KVM under memory pressure, with THP enabled on the host,
we noticed that MMU notifier took a long time to invalidate huge pages.
Since the invalidation was done with mmu_lock held, it not only wasted
the CPU but also made the host harder to respond.
This patch mitigates this by using kvm_handle_hva_range().
Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
|
| /openbmc/linux/virt/kvm/ |
| H A D | kvm_main.c | diff b3ae2096974b12c3af2ad1a4e7716b084949867f Mon Jul 02 03:56:33 CDT 2012 Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp> KVM: Introduce kvm_unmap_hva_range() for kvm_mmu_notifier_invalidate_range_start()
When we tested KVM under memory pressure, with THP enabled on the host,
we noticed that MMU notifier took a long time to invalidate huge pages.
Since the invalidation was done with mmu_lock held, it not only wasted
the CPU but also made the host harder to respond.
This patch mitigates this by using kvm_handle_hva_range().
Signed-off-by: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: Alexander Graf <agraf@suse.de>
Cc: Paul Mackerras <paulus@samba.org>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
|