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: Fri, 07 Feb 2014 12:00:40 +0100	[thread overview]
Message-ID: <52F4BCD8.5020400@suse.de> (raw)
In-Reply-To: <52F4B84D.9040901@redhat.com>

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!

Apart from Anthony or someone having to do the actual conversion at some
point, the big unanswered question is how do we share code between PCI
bus hosts - for PCI host bridges we can place code in the QOM base type
(think realizing PCIBus with Bandan's series (which I have been refining
the last few days)), but for PCI-PCI bridges where there's two that's
gonna be slightly more difficult sharing-wise.

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-07 11: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
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 [this message]
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=52F4BCD8.5020400@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.