From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@linux.vnet.ibm.com, andreas.faerber@web.de,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qdev: give all devices a canonical QOM path
Date: Tue, 27 Mar 2012 11:42:49 -0500 [thread overview]
Message-ID: <4F71EE09.8000407@codemonkey.ws> (raw)
In-Reply-To: <1332866328-25443-1-git-send-email-pbonzini@redhat.com>
On 03/27/2012 11:38 AM, Paolo Bonzini wrote:
> A strong limitation of QOM right now is that unconverted ports
> (e.g. all...) do not give a canonical path to devices that are
> part of the board. This in turn makes it impossible to replace
> PROP_PTR with a QOM link for example.
>
> This series fixes this by putting all such devices under a
> /unattached container.
Excellent! Thanks for doing this.
Regards,
Anthony Liguori
>
> The problem is when to do this. qdev_init is a good place, but it
> requires the composition tree to be in order by the time we call it.
> This is not the case so far, but it can be changed easily (patch 2) at
> the cost of removing most of the few composition examples that are in the
> tree. This change is also necessary so that a single set of the topmost
> realize property can propagate all the way down the composition tree,
> as agreed on the mailing list.
>
> At the end of the series, all devices are moved to /machine
> in order to avoid cluttering too much the QOM root.
>
> Paolo Bonzini (4):
> qom: add container_get
> qdev: add children before qdev_init
> qdev: give all devices a canonical path
> qdev: put all devices under /machine
>
> hw/pc_piix.c | 18 +-----------------
> hw/piix_pci.c | 3 +--
> hw/ppc_prep.c | 2 +-
> hw/qdev-monitor.c | 16 ++++++----------
> hw/qdev.c | 16 +++++++++++++---
> include/qemu/object.h | 24 ++++++++++++++++++++++++
> qom/container.c | 23 +++++++++++++++++++++++
> qom/object.c | 33 +++++++++++++++++----------------
> 8 files changed, 86 insertions(+), 49 deletions(-)
>
next prev parent reply other threads:[~2012-03-27 16:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 16:38 [Qemu-devel] [PATCH 0/4] qdev: give all devices a canonical QOM path Paolo Bonzini
2012-03-27 16:38 ` [Qemu-devel] [PATCH 1/4] qom: add container_get Paolo Bonzini
2012-03-27 21:07 ` Anthony Liguori
2012-03-27 16:38 ` [Qemu-devel] [PATCH 2/4] qdev: add children before qdev_init Paolo Bonzini
2012-03-27 21:08 ` Anthony Liguori
2012-03-27 16:38 ` [Qemu-devel] [PATCH 3/4] qdev: give all devices a canonical path Paolo Bonzini
2012-03-27 21:12 ` Anthony Liguori
2012-03-27 16:38 ` [Qemu-devel] [PATCH 4/4] qdev: put all devices under /machine Paolo Bonzini
2012-03-27 21:11 ` Anthony Liguori
2012-03-28 14:01 ` Andreas Färber
2012-03-28 14:34 ` [Qemu-devel] [PATCH v2 " Paolo Bonzini
2012-03-28 15:10 ` Andreas Färber
2012-03-28 15:19 ` Paolo Bonzini
2012-04-05 11:21 ` [Qemu-devel] [PATCH] qom: Refine container_get() to allow using a custom root Andreas Färber
2012-04-05 11:30 ` Paolo Bonzini
2012-03-27 16:42 ` Anthony Liguori [this message]
2012-04-02 21:21 ` [Qemu-devel] [PATCH 0/4] qdev: give all devices a canonical QOM path Anthony Liguori
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=4F71EE09.8000407@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@linux.vnet.ibm.com \
--cc=andreas.faerber@web.de \
--cc=pbonzini@redhat.com \
--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).