From: Marcelo Tosatti <mtosatti@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 0/4] qemu-kvm: prepare for adding eventfd usage to upstream
Date: Sat, 13 Feb 2010 11:26:07 -0200 [thread overview]
Message-ID: <20100213132607.GA18552@amt.cnet> (raw)
In-Reply-To: <1265843356-25765-1-git-send-email-pbonzini@redhat.com>
On Thu, Feb 11, 2010 at 12:09:12AM +0100, Paolo Bonzini wrote:
> This patch series morphs the code in qemu-kvm's eventfd so that it looks
> like the code in upstream qemu. Patch 4 is not yet in upstream QEMU,
> I'm submitting it first to qemu-kvm to avoid conflicts.
>
> Paolo Bonzini (4):
> morph qemu_kvm_notify_work into qemu.git's qemu_event_increment
> morph io_thread_wakeup into qemu.git's qemu_event_read
> fix placement of config-host.h inclusion
> move qemu_eventfd to osdep.c
>
> compatfd.c | 26 --------------------------
> compatfd.h | 2 --
> osdep.c | 37 +++++++++++++++++++++++++++++++++++--
> qemu-common.h | 1 +
> qemu-kvm.c | 50 +++++++++++++++++---------------------------------
> 5 files changed, 53 insertions(+), 63 deletions(-)
Looks good to me.
next prev parent reply other threads:[~2010-02-13 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 23:09 [Qemu-devel] [PATCH 0/4] qemu-kvm: prepare for adding eventfd usage to upstream Paolo Bonzini
2010-02-10 23:09 ` [Qemu-devel] [PATCH 1/4] qemu-kvm: morph qemu_kvm_notify_work into qemu.git's qemu_event_increment Paolo Bonzini
2010-02-10 23:09 ` [Qemu-devel] [PATCH 2/4] qemu-kvm: morph io_thread_wakeup into qemu.git's qemu_event_read Paolo Bonzini
2010-02-10 23:09 ` [Qemu-devel] [PATCH 3/4] qemu-kvm: fix placement of config-host.h inclusion Paolo Bonzini
2010-02-10 23:09 ` [Qemu-devel] [PATCH 4/4] qemu-kvm: move qemu_eventfd to osdep.c Paolo Bonzini
2010-02-13 13:26 ` Marcelo Tosatti [this message]
2010-02-14 12:32 ` [Qemu-devel] Re: [PATCH 0/4] qemu-kvm: prepare for adding eventfd usage to upstream Avi Kivity
2010-02-17 12:53 ` 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=20100213132607.GA18552@amt.cnet \
--to=mtosatti@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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).