From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gleb Natapov <gleb@redhat.com>, Avi Kivity <avi@redhat.com>,
kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] uq/master: KVM: Request setting of nmi_pending and sipi_vector
Date: Thu, 28 Jan 2010 17:58:37 -0200 [thread overview]
Message-ID: <20100128195837.GA18856@amt.cnet> (raw)
In-Reply-To: <4B614B3B.1040606@siemens.com>
On Thu, Jan 28, 2010 at 09:30:51AM +0100, Jan Kiszka wrote:
> The final version of VCPU events in 2.6.33 will allow to skip
> nmi_pending and sipi_vector on KVM_SET_VCPU_EVENTS. For now let's write
> them unconditionally, which is unproblematic for upstream due to missing
> SMP support. Future version which enable SMP will write them only on
> reset.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Applied, thanks.
prev parent reply other threads:[~2010-01-28 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 8:30 [Qemu-devel] [PATCH] uq/master: KVM: Request setting of nmi_pending and sipi_vector Jan Kiszka
2010-01-28 19:58 ` Marcelo Tosatti [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=20100128195837.GA18856@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).