From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Amit Shah <amit.shah@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 4/4] vl: add -late-object to create QOM objects after machine init
Date: Mon, 02 Jul 2012 14:35:10 +0200 [thread overview]
Message-ID: <4FF1957E.1050301@suse.de> (raw)
In-Reply-To: <4FF194CA.3090404@redhat.com>
Am 02.07.2012 14:32, schrieb Paolo Bonzini:
> Il 26/06/2012 00:43, 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...
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-07-02 12:35 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 [this message]
2012-09-18 23:07 ` Anthony Liguori
2012-09-19 7:27 ` Paolo Bonzini
[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=4FF1957E.1050301@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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.