From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 0/5] qcow2.py: dump metadata
Date: Mon, 22 Apr 2013 14:38:09 +0200 [thread overview]
Message-ID: <20130422123809.GC21317@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1366298249-11739-1-git-send-email-pbonzini@redhat.com>
On Thu, Apr 18, 2013 at 05:17:24PM +0200, Paolo Bonzini wrote:
> 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.
The patches look sane by themselves but it would be nicer to integrate
with qemu-img by extending the block layer C code rather than
reimplementing part of the block layer in Python for this single command.
Stefan
prev parent reply other threads:[~2013-04-22 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 15:17 [Qemu-devel] [RFC PATCH 0/5] qcow2.py: dump metadata Paolo Bonzini
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 ` 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=20130422123809.GC21317@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=kwolf@redhat.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).