From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, armbru@redhat.com, aliguori@amazon.com,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] scripts: Add qom-tree script as modern equivalent of info qtree
Date: Wed, 05 Feb 2014 18:55:40 +0100 [thread overview]
Message-ID: <52F27B1C.6010307@redhat.com> (raw)
In-Reply-To: <52F27A1D.2040504@suse.de>
Il 05/02/2014 18:51, Andreas Färber ha scritto:
>> > So, even though I think this script is a very welcome addition, I don't
>> > think it helps settling the question of what to do with "info qtree".
>> > IMO there's no good reason to exclude busless devices from "info qtree",
>> > and it's a bug (of course less severe than crashing, but still a bug)
>> > that the busless nand device doesn't appear there.
> Don't you see that that is unfixable? We may be able to replace info
> qtree by an info qom-tree, which does the equivalent of this QMP-based
> script, but qtree ues a completely different display hierarchy than QOM.
Yes, that's why it's useful. :)
Busless devices can still be listed, either under their parent or as
siblings of the system bus.
Paolo
next prev parent reply other threads:[~2014-02-05 17:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 17:35 [Qemu-devel] [PATCH] scripts: Add qom-tree script as modern equivalent of info qtree Andreas Färber
2014-02-05 17:48 ` Paolo Bonzini
2014-02-05 17:51 ` Andreas Färber
2014-02-05 17:55 ` Paolo Bonzini [this message]
2014-02-05 18:01 ` Andreas Färber
2014-02-07 7:13 ` Paolo Bonzini
2014-02-07 11:09 ` Andreas Färber
2014-02-07 11:21 ` Paolo Bonzini
2014-02-07 12:44 ` Andreas Färber
2014-02-07 13:06 ` Paolo Bonzini
2014-02-07 13:48 ` Andreas Färber
2014-02-07 14:18 ` Paolo Bonzini
2014-02-07 15:00 ` Markus Armbruster
2014-02-07 12:49 ` Andreas Färber
2014-02-07 13:16 ` Paolo Bonzini
2014-02-05 17:56 ` Andreas Färber
2014-02-05 17:58 ` Paolo Bonzini
2014-02-05 18:08 ` Andreas Färber
2014-02-07 10:41 ` Paolo Bonzini
2014-02-07 11:00 ` Andreas Färber
2014-02-07 11:10 ` Paolo Bonzini
2014-02-05 18:24 ` Eric Blake
2014-02-05 18:39 ` Andreas Färber
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=52F27B1C.6010307@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).