When async_pf is ready the guest needs to be made aware of it ASAP, because it may be holding off a higher priority task pending the async_pf resolution in favor of a lower priority one. In case async_pf's are harvested in vcpu context (x86) we have to not only wake the vcpu up but kick it into host. Signed-off-by: Roman Kagan <rkagan@xxxxxxxxxxxxx> Cc: Christian Borntraeger <borntraeger@xxxxxxxxxx> --- v1 -> v2: - do not break s390 build by using kvm_vcpu_wakeup (Christian) virt/kvm/async_pf.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/virt/kvm/async_pf.c b/virt/kvm/async_pf.c index 9cced14..b5b9cca 100644 --- a/virt/kvm/async_pf.c +++ b/virt/kvm/async_pf.c @@ -105,8 +105,12 @@ static void async_pf_execute(struct work_struct *work) * This memory barrier pairs with prepare_to_wait's set_current_state() */ smp_mb(); +#ifdef CONFIG_KVM_ASYNC_PF_SYNC if (swait_active(&vcpu->wq)) swake_up(&vcpu->wq); +#else + kvm_vcpu_kick(vcpu); +#endif mmput(mm); kvm_put_kvm(vcpu->kvm); -- 2.9.3 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
