From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates
Date: Mon, 14 Dec 2009 12:34:22 +0200 [thread overview]
Message-ID: <4B2614AE.9010204@redhat.com> (raw)
In-Reply-To: <4B26144E.6040503@siemens.com>
On 12/14/2009 12:32 PM, Jan Kiszka wrote:
> Jan Kiszka wrote:
>
>> User space may not want to overwrite asynchronously changing VCPU event
>> states on write-back. So allow to skip nmi.pending and sipi_vector by
>> setting corresponding bits in the flags field of kvm_vcpu_events.
>>
>>
> What will happen to this patch now? Merge during 2.6.33 window or drop?
>
I'll merge it into 2.6.33.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-12-14 10:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 16:55 [PATCH] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates Jan Kiszka
2009-12-06 17:05 ` Avi Kivity
2009-12-06 17:12 ` Jan Kiszka
2009-12-15 14:54 ` Avi Kivity
2009-12-15 16:41 ` Jan Kiszka
2009-12-15 17:08 ` Avi Kivity
2009-12-15 22:57 ` [PATCH] KVM: x86: Adjust KVM_VCPUEVENT flag names Jan Kiszka
2009-12-16 9:59 ` Avi Kivity
2009-12-06 17:24 ` [PATCH v2] KVM: x86: Extend KVM_SET_VCPU_EVENTS with selective updates Jan Kiszka
2009-12-08 14:02 ` Marcelo Tosatti
2009-12-08 14:07 ` Avi Kivity
2009-12-08 20:52 ` Marcelo Tosatti
2009-12-08 21:17 ` Jan Kiszka
2009-12-15 14:50 ` Avi Kivity
2009-12-15 16:43 ` Jan Kiszka
2009-12-15 17:10 ` Avi Kivity
2009-12-15 17:29 ` Jan Kiszka
2009-12-14 10:32 ` [PATCH] " Jan Kiszka
2009-12-14 10:34 ` 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=4B2614AE.9010204@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.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).