aboutsummaryrefslogtreecommitdiff
path: root/virt/kvm/Kconfig
diff options
context:
space:
mode:
authorDominik Dingel <dingel@linux.vnet.ibm.com>2013-06-06 15:32:37 +0200
committerChristian Borntraeger <borntraeger@de.ibm.com>2014-01-30 12:51:38 +0100
commite0ead41a6dac09f86675ce07a66e4b253a9b7bd5 (patch)
treeed0026f1f858cbab03db7dc83cb7820d0a348821 /virt/kvm/Kconfig
parent24eb3a824c4f3ccfaa2305dc1d9d9e2a708828c5 (diff)
downloadlinux-linaro-stable-e0ead41a6dac09f86675ce07a66e4b253a9b7bd5.tar.gz
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>
Diffstat (limited to 'virt/kvm/Kconfig')
-rw-r--r--virt/kvm/Kconfig4
1 files changed, 4 insertions, 0 deletions
diff --git a/virt/kvm/Kconfig b/virt/kvm/Kconfig
index fbe1a48bd629..13f2d19793e3 100644
--- a/virt/kvm/Kconfig
+++ b/virt/kvm/Kconfig
@@ -22,6 +22,10 @@ config KVM_MMIO
config KVM_ASYNC_PF
bool
+# Toggle to switch between direct notification and batch job
+config KVM_ASYNC_PF_SYNC
+ bool
+
config HAVE_KVM_MSI
bool