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)
committerChristoffer Dall <christoffer.dall@linaro.org>
Thu, 2 Oct 2014 15:18:30 +0000 (17:18 +0200)
commite9aa8f627c7c504c3880acdfa57849bd3d75dc83
tree0cb01449c80378c701da4ccd908424983dab634d
parent031cbab9d6d2a6beca9e19472a40f5e22ecfbe07
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>
(cherry picked from commit e0ead41a6dac09f86675ce07a66e4b253a9b7bd5)
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
arch/x86/kvm/mmu.c
include/linux/kvm_host.h
virt/kvm/Kconfig
virt/kvm/async_pf.c