From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>, 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:51:25 +0100 [thread overview]
Message-ID: <52F27A1D.2040504@suse.de> (raw)
In-Reply-To: <52F2795D.10708@redhat.com>
Am 05.02.2014 18:48, schrieb Paolo Bonzini:
> Il 05/02/2014 18:35, Andreas Färber ha scritto:
>> Functionally it is a recursive qom-list with qom-get per non-child<>
>> property. Some failures needed to be handled, such as trying to read a
>> pointer property, which is not representable in QMP. Those print a
>> literal "<EXCEPTION>".
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>
> I don't think it's a modern equivalent of anything. The two are just
> different.
>
> "info qtree" may be focused the old concept of buses, but those buses
> aren't going anywhere anytime soon. "info qtree" may also be focused on
> the old concept of qdev properties (now "static" properties), but that's
> not something that cannot be fixed.
>
> 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.
Andreas
>
> We can apply all three patches:
>
> * qdev_try_create for busless devices (or alternatively abort when
> creating the device, qom-test will catch that)
>
> * add qom-tree
>
> * nand: Don't use qdev_create() in nand_init()
>
> and still improve "info qtree" on top.
>
> Paolo
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-02-05 17:51 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 [this message]
2014-02-05 17:55 ` Paolo Bonzini
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=52F27A1D.2040504@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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 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.