From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, nsoffer@redhat.com, vsementsov@virtuozzo.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: [PATCH v5 0/5] qemu-img: Add convert --bitmaps
Date: Wed, 20 May 2020 17:01:13 -0500 [thread overview]
Message-ID: <20200520220118.1037094-1-eblake@redhat.com> (raw)
v4 was here:
https://lists.gnu.org/archive/html/qemu-devel/2020-05/msg03182.html
original cover letter here:
https://lists.gnu.org/archive/html/qemu-devel/2020-04/msg03464.html
Based-on: <20200519175707.815782-1-eblake@redhat.com>
[pull v3 bitmaps patches for 2020-05-18]
Since then:
- patch 1 is new (fixes regression from recent NBD pull)
- patch 2, 4: include fixes suggested by Vladimir; biggest is that
bitmaps computation is now in qcow2-bitmaps.c instead of qcow2.c
- patch 3: split out from patch 4 (was v4 8/9)
- patch 5: rebase to master
001/5:[down] 'iotests: Fix test 178'
002/5:[0106] [FC] 'qcow2: Expose bitmaps' size during measure'
003/5:[down] 'qemu-img: Factor out code for merging bitmaps'
004/5:[0012] [FC] 'qemu-img: Add convert --bitmaps option'
005/5:[0002] [FC] 'iotests: Add test 291 to for qemu-img bitmap coverage'
Series can also be downloaded at:
https://repo.or.cz/qemu/ericb.git/shortlog/refs/tags/qemu-img-bitmaps-v5
Eric Blake (5):
iotests: Fix test 178
qcow2: Expose bitmaps' size during measure
qemu-img: Factor out code for merging bitmaps
qemu-img: Add convert --bitmaps option
iotests: Add test 291 to for qemu-img bitmap coverage
docs/tools/qemu-img.rst | 18 ++++-
qapi/block-core.json | 15 ++--
block/qcow2.h | 2 +
block/crypto.c | 2 +-
block/qcow2-bitmap.c | 36 +++++++++
block/qcow2.c | 14 +++-
block/raw-format.c | 2 +-
qemu-img.c | 135 +++++++++++++++++++++++++++----
qemu-img-cmds.hx | 8 +-
tests/qemu-iotests/178.out.qcow2 | 18 ++++-
tests/qemu-iotests/178.out.raw | 2 +-
tests/qemu-iotests/190 | 58 ++++++++++++-
tests/qemu-iotests/190.out | 35 +++++++-
tests/qemu-iotests/291 | 112 +++++++++++++++++++++++++
tests/qemu-iotests/291.out | 80 ++++++++++++++++++
tests/qemu-iotests/group | 1 +
16 files changed, 501 insertions(+), 37 deletions(-)
create mode 100755 tests/qemu-iotests/291
create mode 100644 tests/qemu-iotests/291.out
--
2.26.2
next reply other threads:[~2020-05-20 22:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 22:01 Eric Blake [this message]
2020-05-20 22:01 ` [PATCH v5 1/5] iotests: Fix test 178 Eric Blake
2020-05-21 11:31 ` Vladimir Sementsov-Ogievskiy
2020-05-20 22:01 ` [PATCH v5 2/5] qcow2: Expose bitmaps' size during measure Eric Blake
2020-05-20 23:00 ` Nir Soffer
2020-05-21 11:40 ` Vladimir Sementsov-Ogievskiy
2020-05-21 13:29 ` Nir Soffer
2020-05-21 15:09 ` Vladimir Sementsov-Ogievskiy
2020-05-21 16:28 ` Nir Soffer
2020-05-21 13:08 ` Eric Blake
2020-05-21 13:17 ` Nir Soffer
2020-05-21 13:29 ` Eric Blake
2020-05-20 22:01 ` [PATCH v5 3/5] qemu-img: Factor out code for merging bitmaps Eric Blake
2020-05-20 22:01 ` [PATCH v5 4/5] qemu-img: Add convert --bitmaps option Eric Blake
2020-05-21 15:11 ` Nir Soffer
2020-05-21 15:19 ` Eric Blake
2020-05-20 22:01 ` [PATCH v5 5/5] iotests: Add test 291 to for qemu-img bitmap coverage Eric Blake
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=20200520220118.1037094-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=nsoffer@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).