From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
qemu-devel@nongnu.org, mreitz@redhat.com,
andrey.shinkevich@virtuozzo.com, den@openvz.org
Subject: [PATCH v7 0/9] iotests: Dump QCOW2 dirty bitmaps metadata
Date: Fri, 12 Jun 2020 03:04:53 +0300 [thread overview]
Message-ID: <1591920302-1002219-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
Note: based on the Vladimir's series
[v5 00/13] iotests: Dump QCOW2 dirty bitmaps metadata
Add dirty bitmap information to QCOW2 metadata dump in the qcow2_format.py.
v7:
01: Fix for magic hexadecimal output in 291
02: Bitmap table output format improvement.
03: Incremental change in the test 291 output.
v6:
01: Fixing capitalization of header extension constant.
(Suggested by Eric)
02: The cluster size global variable discarded and passed as a parameter.
03: Re-based to Vladimir's v5 series.
04: The code of passing qcow2.py JSON format key moved to separate patch.
05: Making dict(s) for dumping in JSON format was substituted with a copy
of __dict__.
v5: The Vladimir's preliminary series
v4: The Vladimir's preliminary series
Andrey Shinkevich (9):
iotests: Fix for magic hexadecimal output in 291
qcow2: Fix capitalization of header extension constant.
qcow2_format.py: make printable data an extension class member
qcow2_format.py: Dump bitmap directory information
qcow2_format.py: pass cluster size to substructures
qcow2_format.py: Dump bitmap table serialized entries
qcow2.py: Introduce '-j' key to dump in JSON format
qcow2_format.py: collect fields to dump in JSON format
qcow2_format.py: support dumping metadata in JSON format
block/qcow2.c | 2 +-
docs/interop/qcow2.txt | 2 +-
tests/qemu-iotests/291.out | 112 ++++++++++++++++++-
tests/qemu-iotests/qcow2.py | 20 +++-
tests/qemu-iotests/qcow2_format.py | 217 ++++++++++++++++++++++++++++++++++---
5 files changed, 327 insertions(+), 26 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-06-12 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 0:04 Andrey Shinkevich [this message]
2020-06-12 0:04 ` [PATCH v7 1/9] iotests: Fix for magic hexadecimal output in 291 Andrey Shinkevich
2020-06-15 9:43 ` Vladimir Sementsov-Ogievskiy
2020-06-12 0:04 ` [PATCH v7 2/9] qcow2: Fix capitalization of header extension constant Andrey Shinkevich
2020-06-15 9:44 ` Vladimir Sementsov-Ogievskiy
2020-06-12 0:04 ` [PATCH v7 3/9] qcow2_format.py: make printable data an extension class member Andrey Shinkevich
2020-06-15 9:47 ` Vladimir Sementsov-Ogievskiy
2020-06-12 0:04 ` [PATCH v7 4/9] qcow2_format.py: Dump bitmap directory information Andrey Shinkevich
2020-06-15 10:34 ` Vladimir Sementsov-Ogievskiy
2020-06-12 0:04 ` [PATCH v7 5/9] qcow2_format.py: pass cluster size to substructures Andrey Shinkevich
2020-06-12 0:04 ` [PATCH v7 6/9] qcow2_format.py: Dump bitmap table serialized entries Andrey Shinkevich
2020-06-12 0:05 ` [PATCH v7 7/9] qcow2.py: Introduce '-j' key to dump in JSON format Andrey Shinkevich
2020-06-12 0:05 ` [PATCH v7 8/9] qcow2_format.py: collect fields " Andrey Shinkevich
2020-06-12 0:05 ` [PATCH v7 9/9] qcow2_format.py: support dumping metadata " Andrey Shinkevich
2020-06-15 9:42 ` [PATCH v7 0/9] iotests: Dump QCOW2 dirty bitmaps metadata Vladimir Sementsov-Ogievskiy
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=1591920302-1002219-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=den@openvz.org \
--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).