qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, hch@lst.de
Subject: [Qemu-devel] [RFC PATCH 0/5] block: Format/protocol split
Date: Wed, 14 Apr 2010 17:50:09 +0200	[thread overview]
Message-ID: <1271260214-27443-1-git-send-email-kwolf@redhat.com> (raw)

This is the next version of the format/protocol split RFC that Christoph posted
on Monday. I did fix image creation in his original patch and added some
additional patches for more cleanup and to fix the no_zero_init bug that is
mentioned in the commit log of this first patch.

One point that still needs to be done is converting all the random format
drivers that noone uses to use block.c functions instead of POSIX functions.
In some points they look like protocol drivers rather than format drivers
otherwise.

If there are no other important issues left, I'm going to merge this into the
block branch soon.

Christoph Hellwig (1):
  block: separate raw images from the file protocol

Kevin Wolf (4):
  block: Split bdrv_open
  block: Avoid forward declaration of bdrv_open_common
  block: Open the underlying image file in generic code
  block: bdrv_has_zero_init

 Makefile.objs          |    2 +-
 block.c                |  266 ++++++++++++++++++++++++++++++++----------------
 block.h                |    2 +
 block/blkdebug.c       |   17 +--
 block/bochs.c          |    2 +-
 block/cloop.c          |    2 +-
 block/cow.c            |    2 +-
 block/curl.c           |   10 +-
 block/dmg.c            |    2 +-
 block/nbd.c            |    2 +-
 block/parallels.c      |    2 +-
 block/qcow.c           |   69 ++++++-------
 block/qcow2-cluster.c  |   64 ++++++------
 block/qcow2-refcount.c |   80 +++++++-------
 block/qcow2-snapshot.c |   22 ++--
 block/qcow2.c          |   67 +++++-------
 block/qcow2.h          |    2 +-
 block/raw-posix.c      |   25 +++--
 block/raw-win32.c      |   16 ++--
 block/raw.c            |  144 ++++++++++++++++++++++++++
 block/vdi.c            |   30 ++----
 block/vmdk.c           |    2 +-
 block/vpc.c            |   34 +++----
 block/vvfat.c          |    2 +-
 block_int.h            |    5 +-
 qemu-img.c             |    6 +-
 26 files changed, 544 insertions(+), 333 deletions(-)
 create mode 100644 block/raw.c

             reply	other threads:[~2010-04-14 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 15:50 Kevin Wolf [this message]
2010-04-14 15:50 ` [Qemu-devel] [RFC PATCH 1/5] block: separate raw images from the file protocol Kevin Wolf
2010-04-14 18:36   ` Stefan Hajnoczi
2010-04-14 15:50 ` [Qemu-devel] [RFC PATCH 2/5] block: Split bdrv_open Kevin Wolf
2010-04-14 15:50 ` [Qemu-devel] [RFC PATCH 3/5] block: Avoid forward declaration of bdrv_open_common Kevin Wolf
2010-04-14 15:50 ` [Qemu-devel] [RFC PATCH 4/5] block: Open the underlying image file in generic code Kevin Wolf
2010-04-15  8:48   ` Stefan Hajnoczi
2010-04-14 15:50 ` [Qemu-devel] [RFC PATCH 5/5] block: bdrv_has_zero_init Kevin Wolf

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=1271260214-27443-1-git-send-email-kwolf@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hch@lst.de \
    --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).