From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, marcelo@redhat.com
Subject: Re: [PATCH] async PF event can fail to wakeup vcpu from halt
Date: Sun, 06 May 2012 14:57:12 +0300 [thread overview]
Message-ID: <4FA66718.5060603@redhat.com> (raw)
In-Reply-To: <20120503083639.GT22191@redhat.com>
On 05/03/2012 11:36 AM, Gleb Natapov wrote:
> If vcpu executes hlt instruction while async PF is waiting to be delivered
> vcpu can block and deliver async PF only after another even wakes it
> up. This happens because kvm_check_async_pf_completion() will remove
> completion event from vcpu->async_pf.done before entering kvm_vcpu_block()
> and this will make kvm_arch_vcpu_runnable() return false. The solution
> is to make vcpu runnable when processing completion.
>
>
Thanks, applied to master for 3.4.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-05-06 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 8:36 [PATCH] async PF event can fail to wakeup vcpu from halt Gleb Natapov
2012-05-06 11:57 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA66718.5060603@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcelo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).