From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Amit Shah" <amit.shah@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 4/4] vl: add -late-object to create QOM objects after machine init
Date: Wed, 19 Sep 2012 09:27:14 +0200 [thread overview]
Message-ID: <505973D2.1080407@redhat.com> (raw)
In-Reply-To: <87boh39bhg.fsf@codemonkey.ws>
Il 19/09/2012 01:07, Anthony Liguori ha scritto:
>>>> In order to create qdev objects via -late-object, we almost always have to
>>>> >>> specify the parent_bus which is usually created during machine init. Until we
>>>> >>> properly support two stage init, introduce a -late-object option that allows for
>>>> >>> creation of objects post-machine init.
>>> >>
>>> >> This is only needed for -device, no? So we can avoid introducing it and
>>> >> just use -device.
>> >
>> > +1, was thinking along the same lines...
> Sorry for such a delayed response...
>
> The semantics of how -device is different in that it implies realize.
Yes, all I'm saying is, I don't see a need for -late-object since it is
only needed for devices and we have a separate method to create them.
Paolo
next prev parent reply other threads:[~2012-09-19 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340664222-25098-1-git-send-email-aliguori@us.ibm.com>
[not found] ` <1340664222-25098-5-git-send-email-aliguori@us.ibm.com>
2012-07-02 12:32 ` [Qemu-devel] [PATCH 4/4] vl: add -late-object to create QOM objects after machine init Paolo Bonzini
2012-07-02 12:35 ` Andreas Färber
2012-09-18 23:07 ` Anthony Liguori
2012-09-19 7:27 ` Paolo Bonzini [this message]
[not found] ` <1340664222-25098-3-git-send-email-aliguori@us.ibm.com>
2012-07-02 12:32 ` [Qemu-devel] [PATCH 2/4] qdev: add realized property and make adding child bus implied by realize Paolo Bonzini
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=505973D2.1080407@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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.