From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 00/21] Add qemu-img subcommand to dump file metadata
Date: Thu, 5 Sep 2013 15:55:19 +0200 [thread overview]
Message-ID: <20130905135519.GA5005@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1378314038-15525-1-git-send-email-pbonzini@redhat.com>
On Wed, Sep 04, 2013 at 07:00:17PM +0200, Paolo Bonzini wrote:
> v4->v5: no change except for context and correcting the "Since: 1.6"
> in qapi-schema.json
>
> Paolo Bonzini (21):
> cow: make reads go at a decent speed
> cow: make writes go at a less indecent speed
> cow: do not call bdrv_co_is_allocated
> block: keep bs->total_sectors up to date even for growable block
> devices
> block: make bdrv_co_is_allocated static
> block: do not use ->total_sectors in bdrv_co_is_allocated
> block: remove bdrv_is_allocated_above/bdrv_co_is_allocated_above
> distinction
> block: expect errors from bdrv_co_is_allocated
> qemu-img: always probe the input image for allocated sectors
> block: make bdrv_has_zero_init return false for copy-on-write-images
> block: introduce bdrv_get_block_status API
> block: define get_block_status return value
> block: return get_block_status data and flags for formats
> block: use bdrv_has_zero_init to return BDRV_BLOCK_ZERO
> block: return BDRV_BLOCK_ZERO past end of backing file
> qemu-img: add a "map" subcommand
> docs, qapi: document qemu-img map
> raw-posix: return get_block_status data and flags
> raw-posix: report unwritten extents as zero
> block: add default get_block_status implementation for protocols
> block: look for zero blocks in bs->file
>
> block.c | 174 +++++++++++++++++++--------------
> block/backup.c | 4 +-
> block/commit.c | 6 +-
> block/cow.c | 91 +++++++++++++-----
> block/mirror.c | 4 +-
> block/qcow.c | 13 ++-
> block/qcow2.c | 24 +++--
> block/qed.c | 39 ++++++--
> block/raw-posix.c | 24 +++--
> block/raw_bsd.c | 10 +-
> block/sheepdog.c | 14 +--
> block/stream.c | 10 +-
> block/vdi.c | 17 +++-
> block/vmdk.c | 23 ++++-
> block/vvfat.c | 15 +--
> include/block/block.h | 34 +++++--
> include/block/block_int.h | 2 +-
> qapi-schema.json | 29 ++++++
> qemu-img-cmds.hx | 6 ++
> qemu-img.c | 239 +++++++++++++++++++++++++++++++++++++++++-----
> qemu-img.texi | 55 +++++++++++
> qemu-io-cmds.c | 4 +
> 22 files changed, 646 insertions(+), 191 deletions(-)
>
> --
> 1.8.3.1
>
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
prev parent reply other threads:[~2013-09-05 13:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 17:00 [Qemu-devel] [PATCH v5 00/21] Add qemu-img subcommand to dump file metadata Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 01/21] cow: make reads go at a decent speed Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 02/21] cow: make writes go at a less indecent speed Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 03/21] cow: do not call bdrv_co_is_allocated Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 04/21] block: keep bs->total_sectors up to date even for growable block devices Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 05/21] block: make bdrv_co_is_allocated static Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 06/21] block: do not use ->total_sectors in bdrv_co_is_allocated Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 07/21] block: remove bdrv_is_allocated_above/bdrv_co_is_allocated_above distinction Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 08/21] block: expect errors from bdrv_co_is_allocated Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 09/21] qemu-img: always probe the input image for allocated sectors Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 10/21] block: make bdrv_has_zero_init return false for copy-on-write-images Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 11/21] block: introduce bdrv_get_block_status API Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 12/21] block: define get_block_status return value Paolo Bonzini
2014-05-05 14:34 ` Kevin Wolf
2014-05-05 14:58 ` Paolo Bonzini
2014-05-06 11:34 ` Kevin Wolf
2014-05-06 12:31 ` Paolo Bonzini
2014-05-06 13:08 ` Kevin Wolf
2014-05-06 13:20 ` Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 13/21] block: return get_block_status data and flags for formats Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 14/21] block: use bdrv_has_zero_init to return BDRV_BLOCK_ZERO Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 15/21] block: return BDRV_BLOCK_ZERO past end of backing file Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 16/21] qemu-img: add a "map" subcommand Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 17/21] docs, qapi: document qemu-img map Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 18/21] raw-posix: return get_block_status data and flags Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 19/21] raw-posix: report unwritten extents as zero Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 20/21] block: add default get_block_status implementation for protocols Paolo Bonzini
2013-09-04 17:00 ` [Qemu-devel] [PATCH v5 21/21] block: look for zero blocks in bs->file Paolo Bonzini
2013-09-05 13:55 ` Stefan Hajnoczi [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=20130905135519.GA5005@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.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).