From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, davidel@xmailserver.org,
paulmck@linux.vnet.ibm.com, markmc@redhat.com
Subject: Re: [KVM PATCH v5 0/2] iosignalfd
Date: Thu, 04 Jun 2009 15:25:13 +0300 [thread overview]
Message-ID: <4A27BD29.3070709@redhat.com> (raw)
In-Reply-To: <4A26ED22.4060203@novell.com>
Gregory Haskins wrote:
> Marcello, Avi, and myself have previously agreed that Marcello's
> mmio-locking cleanup should go in first. When that happens, I will
> need to rebase this series because it changes how you interface to the
> io_bus code. I should have mentioned that here, but forgot. (Speaking
> of, is there an ETA when that code will be merged Avi?)
>
I had issues with the unbalanced locking the patchset introduced in
coalesced_mmio, once these are resolved the patchset will be merged.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-04 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 20:17 [KVM PATCH v5 0/2] iosignalfd Gregory Haskins
2009-06-03 20:17 ` [KVM PATCH v5 1/2] kvm: make io_bus interface more robust Gregory Haskins
2009-06-03 20:17 ` [KVM PATCH v5 2/2] kvm: add iosignalfd support Gregory Haskins
2009-06-03 20:37 ` Gregory Haskins
2009-06-03 21:45 ` Gregory Haskins
2009-06-04 1:34 ` Paul E. McKenney
2009-06-04 2:55 ` Gregory Haskins
2009-06-04 16:51 ` Paul E. McKenney
2009-06-03 21:37 ` [KVM PATCH v5 0/2] iosignalfd Gregory Haskins
2009-06-04 12:25 ` 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=4A27BD29.3070709@redhat.com \
--to=avi@redhat.com \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.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