From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [RFC PATCH 0/5] qcow2.py: dump metadata
Date: Thu, 18 Apr 2013 17:17:24 +0200 [thread overview]
Message-ID: <1366298249-11739-1-git-send-email-pbonzini@redhat.com> (raw)
This series includes several improvements to qcow2.py, mostly
the ability to dump the L1 and L2 tables for a full backing
chain.
Doing this completely would require support for all image formats,
not just qcow2. To cover the common cases, I included support
for raw backing files.
The right thing to do perhaps would be to add the read-metadata
patches from the in-place QED conversion summer of code project,
but I wanted to throw out these anyway if anyone has comments.
Paolo
Paolo Bonzini (5):
qcow2.py: rename class to Qcow
qcow2.py: add ImageFile superclass
qcow2.py: add load_image() method
qcow2.py: add method to load backing image
qcow2.py: add dump-map command
tests/qemu-iotests/qcow2.py | 258 +++++++++++++++++++++++++++++++++++++-------
1 file changed, 217 insertions(+), 41 deletions(-)
--
1.8.2
next reply other threads:[~2013-04-18 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 15:17 Paolo Bonzini [this message]
2013-04-18 15:17 ` [Qemu-devel] [RFC PATCH 1/5] qcow2.py: rename class to Qcow Paolo Bonzini
2013-04-18 15:17 ` [Qemu-devel] [RFC PATCH 2/5] qcow2.py: add ImageFile superclass Paolo Bonzini
2013-04-18 15:17 ` [Qemu-devel] [RFC PATCH 3/5] qcow2.py: add load_image() method Paolo Bonzini
2013-04-18 15:17 ` [Qemu-devel] [RFC PATCH 4/5] qcow2.py: add method to load backing image Paolo Bonzini
2013-04-18 15:17 ` [Qemu-devel] [RFC PATCH 5/5] qcow2.py: add dump-map command Paolo Bonzini
2013-04-22 12:38 ` [Qemu-devel] [RFC PATCH 0/5] qcow2.py: dump metadata Stefan Hajnoczi
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=1366298249-11739-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@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).