qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 07 Feb 2014 12:10:29 +0100	[thread overview]
Message-ID: <52F4BF25.7020804@redhat.com> (raw)
In-Reply-To: <52F4BCD8.5020400@suse.de>

Il 07/02/2014 12:00, Andreas Färber ha scritto:
> Am 07.02.2014 11:41, schrieb Paolo Bonzini:
>> Il 05/02/2014 19:08, Andreas Färber ha scritto:
>>> http://wiki.qemu.org/Features/QOM#TODO
>>>
>>> Anthony wants buses to go away completely. So that seems a legacy
>>> concept to me even though they do not seem to be gone tomorrow.
>>
>> The way I read that, buses would be replaced by controller devices.
>>
>> This is unrelated to showing the devices according to the bus topology
>> (which still exists in either approach), which is what "info qtree"
>> device.  I guess if controller devices existed, you'd add interfaces
>> like BusProvider and BusChildEnumerator, or equivalently some "magic"
>> properties to do the same, and use that in "info qtree".
>
> Actually my point was that in Anthony's model you get devices on their
> controller device simply by looking at link<foo-device> properties on
> the foo controller device. No special bus code is required any more!

Kind of...  There may still be other links (e.g. to the hotplug handler 
in Igor's series), and you may still want to organize your dump so that 
the bus hierarchy is emphasized.  You cannot unconditionally "expand" 
all links, since they can be recursive.

Paolo

  reply	other threads:[~2014-02-07 11:10 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
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 [this message]
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=52F4BF25.7020804@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).