All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:01:30 +0100	[thread overview]
Message-ID: <52F27C7A.2040701@suse.de> (raw)
In-Reply-To: <52F27B1C.6010307@redhat.com>

Am 05.02.2014 18:55, schrieb Paolo Bonzini:
> 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.

info qtree has been inconclusive for - what? - two years now and no one
has bothered to fix it. If you or Markus care about it, post a patch. :)

The code uses qdev/qbus functions to list those devices so I don't see
an easy way of filtering those devices that qdev/qbus missed and
printing them using the same walking functions. Therefore my saying that
we would need to walk the QOM hierarchy instead, which is
output-incompatible with info qtree and thus a different command.

Not to mention that it will not work for objects that are not devices.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-02-05 18:01 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
2014-02-05 18:01       ` Andreas Färber [this message]
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=52F27C7A.2040701@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.