From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Isaku Yamahata <yamahata@valinux.co.jp>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] kvm: allow arbitrarily sized mmio ioeventfd
Date: Thu, 22 Mar 2012 15:32:43 +0200 [thread overview]
Message-ID: <4F6B29FB.3030505@redhat.com> (raw)
In-Reply-To: <20120320123137.GA29666@redhat.com>
On 03/20/2012 02:31 PM, Michael S. Tsirkin wrote:
> We use a 2 byte ioeventfd for virtio memory,
> add support for this.
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-22 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 12:31 [Qemu-devel] [PATCH] kvm: allow arbitrarily sized mmio ioeventfd Michael S. Tsirkin
2012-03-21 23:34 ` Amos Kong
2012-03-22 13:28 ` Jan Kiszka
2012-03-22 13:28 ` Jan Kiszka
2012-03-22 13:31 ` Avi Kivity
2012-03-22 13:32 ` 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=4F6B29FB.3030505@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=yamahata@valinux.co.jp \
/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).