From: Eduardo Habkost <ehabkost@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, kwolf@redhat.com,
famz@redhat.com, jsnow@redhat.com, armbru@redhat.com,
mreitz@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
crosa@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v3 2/3] scripts: add render_block_graph function for QEMUMachine
Date: Thu, 23 Aug 2018 14:57:23 -0300 [thread overview]
Message-ID: <20180823175723.GP3778@localhost.localdomain> (raw)
In-Reply-To: <20180823154655.40188-3-vsementsov@virtuozzo.com>
On Thu, Aug 23, 2018 at 06:46:54PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Render block nodes graph with help of graphviz. This new function is
> for debugging, so there is no sense to put it into qemu.py as a method
> of QEMUMachine. Let's instead put it separately.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
--
Eduardo
next prev parent reply other threads:[~2018-08-23 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 15:46 [Qemu-devel] [PATCH v3 0/3] block nodes graph visualization Vladimir Sementsov-Ogievskiy
2018-08-23 15:46 ` [Qemu-devel] [PATCH v3 1/3] qapi: add x-debug-query-block-graph Vladimir Sementsov-Ogievskiy
[not found] ` <2a8dda25-67e8-b710-7de3-00f5db68015e@redhat.com>
2018-10-02 13:01 ` Vladimir Sementsov-Ogievskiy
2018-10-05 19:34 ` Max Reitz
2018-10-08 9:40 ` Vladimir Sementsov-Ogievskiy
2018-08-23 15:46 ` [Qemu-devel] [PATCH v3 2/3] scripts: add render_block_graph function for QEMUMachine Vladimir Sementsov-Ogievskiy
2018-08-23 17:56 ` Eduardo Habkost
2018-08-23 17:57 ` Eduardo Habkost [this message]
2018-10-01 19:15 ` Max Reitz
2018-08-23 15:46 ` [Qemu-devel] [PATCH v3 3/3] not-for-commit: example of new command usage for debugging 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=20180823175723.GP3778@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.