From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mtosatti@redhat.com, paulmck@linux.vnet.ibm.com,
markmc@redhat.com
Subject: Re: [PATCHv5 0/6] kvm: locking and API rework for iosignalfd
Date: Wed, 01 Jul 2009 11:10:59 +0300 [thread overview]
Message-ID: <4A4B1A13.3060809@redhat.com> (raw)
In-Reply-To: <20090629192358.GA27464@redhat.com>
On 06/29/2009 10:23 PM, Michael S. Tsirkin wrote:
> This series switches kvm_io_device to slots_lock from kvm->lock mutex,
> and uses that to rework io bus API. This takes less locks on data path,
> and uses less lines of code. These changes will also be useful to serve
> as basis for Greg's iosignalfd work.
>
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-01 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 19:23 [PATCHv5 0/6] kvm: locking and API rework for iosignalfd Michael S. Tsirkin
2009-07-01 8:10 ` Avi Kivity [this message]
2009-07-01 11:59 ` Gregory Haskins
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=4A4B1A13.3060809@redhat.com \
--to=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@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