From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, eblake@redhat.com,
ehabkost@redhat.com, crosa@redhat.com, den@virtuozzo.com
Subject: Re: [Qemu-devel] [PATCH v6 0/3] block nodes graph visualization
Date: Mon, 7 Jan 2019 18:31:04 +0100 [thread overview]
Message-ID: <022ab924-5082-ffc7-9e1d-8633e1a8aa91@redhat.com> (raw)
In-Reply-To: <20181221170909.25584-1-vsementsov@virtuozzo.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
On 21.12.18 18:09, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> On the way of backup schemes development (and in general any complicated
> developments in Qemu block layer) it would be good to have an ability to print
> out graph of block nodes with their permissions.
Thanks, applied patches 1 and 2 to my block branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-07 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 17:09 [Qemu-devel] [PATCH v6 0/3] block nodes graph visualization Vladimir Sementsov-Ogievskiy
2018-12-21 17:09 ` [Qemu-devel] [PATCH v6 1/3] qapi: add x-debug-query-block-graph Vladimir Sementsov-Ogievskiy
2018-12-21 17:09 ` [Qemu-devel] [PATCH v6 2/3] scripts: add render_block_graph function for QEMUMachine Vladimir Sementsov-Ogievskiy
2018-12-21 17:09 ` [Qemu-devel] [PATCH v6 3/3] not-for-commit: example of new command usage for debugging Vladimir Sementsov-Ogievskiy
2019-01-07 17:31 ` Max Reitz [this message]
2019-01-23 9:42 ` [Qemu-devel] [PATCH v6 0/3] block nodes graph visualization Vladimir Sementsov-Ogievskiy
2019-01-23 13:15 ` Max Reitz
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=022ab924-5082-ffc7-9e1d-8633e1a8aa91@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@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).