qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/8] virtio-blk: Converge VirtIOBlockRequest into VirtIOBlockReq
Date: Thu,  5 Jun 2014 09:58:38 +0800	[thread overview]
Message-ID: <1401933526-22436-1-git-send-email-famz@redhat.com> (raw)

This unifies the request structure used by dataplane and non-dataplane code,
while dropping unnessary fields for bounce buffer and read flag.

Applies on top of Stefan's block tree.

v2: Address Paolo's comments. Thanks for reviewing!

[03/08] virtio-blk: Drop bounce buffer from dataplane code
        Moved to front.
[04/08] virtio-blk: Drop VirtIOBlockRequest.read
        Moved to front.
[05/08] virtio-blk: Replace VirtIOBlockRequest with VirtIOBlockReq
        Also drop ->s with ->dev->dataplane.
        Fill in ->dev in dataplane code.
[06/08] virtio-blk: Use VirtIOBlockReq.in to drop VirtIOBlockReq.inhdr
        New.
[07/08] virtio-blk: Convert VirtIOBlockReq.out to structrue
        New.
[08/08] virtio-blk: Fill in VirtIOBlockReq.out in dataplane code
        New.



Fam Zheng (8):
  virtio-blk: Move VirtIOBlockReq to header
  virtio-blk: Convert VirtIOBlockReq.elem to pointer
  virtio-blk: Drop bounce buffer from dataplane code
  virtio-blk: Drop VirtIOBlockRequest.read
  virtio-blk: Replace VirtIOBlockRequest with VirtIOBlockReq
  virtio-blk: Use VirtIOBlockReq.in to drop VirtIOBlockReq.inhdr
  virtio-blk: Convert VirtIOBlockReq.out to structrue
  virtio-blk: Fill in VirtIOBlockReq.out in dataplane code

 hw/block/dataplane/virtio-blk.c | 118 ++++++++++++----------------------------
 hw/block/virtio-blk.c           | 108 ++++++++++++++++++------------------
 include/hw/virtio/virtio-blk.h  |  11 ++++
 3 files changed, 103 insertions(+), 134 deletions(-)

-- 
2.0.0

             reply	other threads:[~2014-06-05  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05  1:58 Fam Zheng [this message]
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 1/8] virtio-blk: Move VirtIOBlockReq to header Fam Zheng
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 2/8] virtio-blk: Convert VirtIOBlockReq.elem to pointer Fam Zheng
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 3/8] virtio-blk: Drop bounce buffer from dataplane code Fam Zheng
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 4/8] virtio-blk: Drop VirtIOBlockRequest.read Fam Zheng
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 5/8] virtio-blk: Replace VirtIOBlockRequest with VirtIOBlockReq Fam Zheng
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 6/8] virtio-blk: Use VirtIOBlockReq.in to drop VirtIOBlockReq.inhdr Fam Zheng
2014-06-05  2:51   ` Paolo Bonzini
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 7/8] virtio-blk: Convert VirtIOBlockReq.out to structrue Fam Zheng
2014-06-05  2:54   ` Paolo Bonzini
2014-06-05  1:58 ` [Qemu-devel] [PATCH v2 8/8] virtio-blk: Fill in VirtIOBlockReq.out in dataplane code Fam Zheng
2014-06-05  2:55   ` Paolo Bonzini
2014-06-05  3:50     ` Fam Zheng
2014-06-05  4:09       ` Paolo Bonzini
2014-06-05  9:20         ` Fam Zheng

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=1401933526-22436-1-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.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).