KVM: async_pf: Provide additional direct page notification
authorDominik Dingel <dingel@linux.vnet.ibm.com>
Thu, 6 Jun 2013 13:32:37 +0000 (15:32 +0200)
committerChristian Borntraeger <borntraeger@de.ibm.com>
Thu, 30 Jan 2014 11:51:38 +0000 (12:51 +0100)
commite0ead41a6dac09f86675ce07a66e4b253a9b7bd5
treeed0026f1f858cbab03db7dc83cb7820d0a348821
parent24eb3a824c4f3ccfaa2305dc1d9d9e2a708828c5
KVM: async_pf: Provide additional direct page notification

By setting a Kconfig option, the architecture can control when
guest notifications will be presented by the apf backend.
There is the default batch mechanism, working as before, where the vcpu
thread should pull in this information.
Opposite to this, there is now the direct mechanism, that will push the
information to the guest.
This way s390 can use an already existing architecture interface.

Still the vcpu thread should call check_completion to cleanup leftovers.

Signed-off-by: Dominik Dingel <dingel@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
arch/x86/kvm/mmu.c
include/linux/kvm_host.h
virt/kvm/Kconfig
virt/kvm/async_pf.c