From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Document KVM_NMI
Date: Wed, 07 Dec 2011 14:20:48 +0200 [thread overview]
Message-ID: <1323260448.4009.8.camel@lappy> (raw)
In-Reply-To: <4EDF5843.6020005@redhat.com>
On Wed, 2011-12-07 at 14:12 +0200, Avi Kivity wrote:
> On 12/07/2011 01:02 PM, Sasha Levin wrote:
> > I don't see the QEMU patch doing a stop before grabbing LAPIC state. Or
> > does it happen somewhere before?
>
> It got dropped on the floor; it's now in next.
I was talking about that patch you merged. I don't see where the vcpu is
being paused before getting the LAPIC state.
--
Sasha.
next prev parent reply other threads:[~2011-12-07 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 10:43 [PATCH] KVM: Document KVM_NMI Avi Kivity
2011-12-07 11:02 ` Sasha Levin
2011-12-07 12:12 ` Avi Kivity
2011-12-07 12:20 ` Sasha Levin [this message]
2011-12-07 12:31 ` Avi Kivity
2011-12-07 12:37 ` Sasha Levin
2011-12-07 12:42 ` Avi Kivity
2011-12-14 18:07 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2011-12-06 20:50 Sasha Levin
2011-12-07 10:21 ` Avi Kivity
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=1323260448.4009.8.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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).