From: Stefan Hajnoczi <stefanha@gmail.com>
To: Pierre Morel <pmorel@linux.vnet.ibm.com>
Cc: cornelia.huck@de.ibm.com, gkurz@linux.vnet.ibm.com,
qemu-devel@nongnu.org, stefanha@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5] virtio dataplane: adapt dataplane for virtio Version 1
Date: Wed, 9 Sep 2015 10:29:51 +0100 [thread overview]
Message-ID: <20150909092951.GH9777@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1441625636-23773-1-git-send-email-pmorel@linux.vnet.ibm.com>
On Mon, Sep 07, 2015 at 01:33:56PM +0200, Pierre Morel wrote:
> Let dataplane allocate different region for the desc/avail/used
> ring regions.
> Take VIRTIO_RING_F_EVENT_IDX into account to increase the used/avail
> rings accordingly.
>
> Signed-off-by: Pierre Morel <pmorel@linux.vnet.ibm.com>
> (changed __virtio16 into uint16_t,
> map descriptor table and available ring read-only)
> Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> ---
>
> Changes from V4:
> - added comments for VIRTIO_RING_F_EVENT_IDX and mapping
> - use uint16_t as in ring definitions instead of __virtio16
> - map descriptor table and available ring read-only
>
> Changes from V3:
> - added changelog
>
> Changes from V2:
> - incorporate the code directly in vring_setup().
> - added room for the event indexes used with VIRTIO_RING_F_EVENT_IDX
>
> Changes from v1:
> - use a macro to gain LOCs inside of vring_setup()
>
> hw/virtio/dataplane/vring.c | 66 +++++++++++++++++++++++++++++--------
> include/hw/virtio/dataplane/vring.h | 4 ++-
> 2 files changed, 55 insertions(+), 15 deletions(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
next prev parent reply other threads:[~2015-09-09 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 11:33 [Qemu-devel] [PATCH v5] virtio dataplane: adapt dataplane for virtio Version 1 Pierre Morel
2015-09-07 15:03 ` Greg Kurz
2015-09-08 7:43 ` Greg Kurz
2015-09-09 9:29 ` Stefan Hajnoczi [this message]
2015-09-09 12:46 ` Greg Kurz
2015-09-09 12:02 ` Michael S. Tsirkin
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=20150909092951.GH9777@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).