qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Eric Blake <eblake@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH v2 00/10] qemu-img: add bitmap info output
Date: Tue, 12 Jun 2018 22:06:03 -0400	[thread overview]
Message-ID: <20180613020613.1343-1-jsnow@redhat.com> (raw)

Allow qemu-img to show information about bitmaps stored in qcow2 images.

v2:
- Remove bitmap manipulation command in favor of a part 2 series later
- Responded to much of Vladimir's feedback (Thank you!);
  - In particular, make sure IN_USE bitmaps cannot be remounted RW.
  - Fixed semantics of the extra_data flag

John Snow (10):
  qcow2/bitmap: remove redundant arguments from bitmap_list_load
  qcow2/bitmap: avoid adjusting bm->flags for RO bitmaps
  qcow2/bitmap: cache bm_list
  qcow2/bitmap: cache loaded bitmaps
  qcow2/bitmap: reject IN_USE bitmaps on rw reload
  qcow2/bitmap: load IN_USE bitmaps if disk is RO
  qcow2/bitmap: track bitmap type
  qcow2/bitmap: track extra_data_size
  qapi: add bitmap info
  qcow2/bitmap: add basic bitmaps info

 block/qcow2-bitmap.c | 276 ++++++++++++++++++++++++++++++++++-----------------
 block/qcow2.c        |   9 ++
 block/qcow2.h        |   3 +
 qapi/block-core.json |  64 +++++++++++-
 4 files changed, 260 insertions(+), 92 deletions(-)

-- 
2.14.3

             reply	other threads:[~2018-06-13  2:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  2:06 John Snow [this message]
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 01/10] qcow2/bitmap: remove redundant arguments from bitmap_list_load John Snow
2018-06-20  9:45   ` Vladimir Sementsov-Ogievskiy
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 02/10] qcow2/bitmap: avoid adjusting bm->flags for RO bitmaps John Snow
2018-06-20 10:01   ` Vladimir Sementsov-Ogievskiy
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 03/10] qcow2/bitmap: cache bm_list John Snow
2018-06-20 13:04   ` Vladimir Sementsov-Ogievskiy
2018-06-20 13:12     ` Vladimir Sementsov-Ogievskiy
2018-06-20 23:29     ` John Snow
2018-06-21 10:25       ` Vladimir Sementsov-Ogievskiy
2018-06-21 21:22         ` John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 04/10] qcow2/bitmap: cache loaded bitmaps John Snow
2018-06-20 13:05   ` Vladimir Sementsov-Ogievskiy
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 05/10] qcow2/bitmap: reject IN_USE bitmaps on rw reload John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 06/10] qcow2/bitmap: load IN_USE bitmaps if disk is RO John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 07/10] qcow2/bitmap: track bitmap type John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 08/10] qcow2/bitmap: track extra_data_size John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 09/10] qapi: add bitmap info John Snow
2018-06-13  2:06 ` [Qemu-devel] [PATCH v2 10/10] qcow2/bitmap: add basic bitmaps info John Snow

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=20180613020613.1343-1-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).