Il 30/01/2014 13:53, Christian Borntraeger ha scritto:
+static inline void kvm_async_page_present_async(struct kvm_vcpu *vcpu,
+ struct kvm_async_pf *work)
+{
+#ifndef CONFIG_KVM_ASYNC_PF_SYNC
+ kvm_arch_async_page_present(vcpu, work);
+#endif
On 31/01/14 12:38, Paolo Bonzini wrote:
Il 30/01/2014 13:53, Christian Borntraeger ha scritto:
+static inline void kvm_async_page_present_async(struct kvm_vcpu *vcpu,
+struct kvm_async_pf *work)
+{
+#ifndef CONFIG_KVM_ASYNC_PF_SYNC
+
Il 31/01/2014 13:24, Christian Borntraeger ha scritto:
On 31/01/14 12:38, Paolo Bonzini wrote:
Il 30/01/2014 13:53, Christian Borntraeger ha scritto:
+static inline void kvm_async_page_present_async(struct kvm_vcpu *vcpu,
+struct kvm_async_pf *work)
+{
+#ifndef
From: Dominik Dingel din...@linux.vnet.ibm.com
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,
