From: Amit Shah <amit.shah@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Cc: Amit Shah <amit.shah@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: [Qemu-devel] [PATCH 0/3] Introduce virtqueue_get_avail_bytes()
Date: Fri, 6 Jul 2012 16:07:06 +0530 [thread overview]
Message-ID: <cover.1341569262.git.amit.shah@redhat.com> (raw)
The current virtqueue_avail_bytes() is a weird API: it's oddly-named:
doesn't tell us what the API is going to do, and also suits just one
use-case (that in virtio-net.c).
Introduce virtqueue_get_avail_bytes(), which returns the number of
bytes in the vq available for input as well as output.
virtqueue_avail_bytes() is made a wrapper around this new function for
now. It should be deprecated soon, though.
Doing this will also help with the virtio-rng patch where a
VirtQueueElement is popped only to find out what its size is. With
this series applied, the popping (and the subsequent save/load of
state for migration) isn't necessary.
The virtio-serial-bus code becomes better too, that's patch 3 here.
Please apply,
Amit Shah (3):
virtio: use unsigned int for counting bytes in vq
virtio: Introduce virtqueue_get_avail_bytes()
virtio-serial-bus: let chardev know the exact number of bytes
requested
hw/virtio-serial-bus.c | 11 +++--------
hw/virtio.c | 30 ++++++++++++++++++++++--------
hw/virtio.h | 5 ++++-
3 files changed, 29 insertions(+), 17 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-07-06 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 10:37 Amit Shah [this message]
2012-07-06 10:37 ` [Qemu-devel] [PATCH 1/3] virtio: use unsigned int for counting bytes in vq Amit Shah
2012-07-06 10:37 ` [Qemu-devel] [PATCH 2/3] virtio: Introduce virtqueue_get_avail_bytes() Amit Shah
2012-07-06 10:37 ` [Qemu-devel] [PATCH 3/3] virtio-serial-bus: let chardev know the exact number of bytes requested Amit Shah
2012-07-16 12:58 ` [Qemu-devel] [PATCH 0/3] Introduce virtqueue_get_avail_bytes() Amit Shah
2012-07-26 14:27 ` Amit Shah
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=cover.1341569262.git.amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=anthony@codemonkey.ws \
--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).