Re: [Qemu-devel] about kvmclock QOM

[Zhi Yong Wu]

On Wed, Mar 14, 2012 at 12:28 AM, Andreas Färber <address@hidden> wrote:
> Am 13.03.2012 16:21, schrieb Zhi Yong Wu:
>> On Tue, Mar 13, 2012 at 11:10 PM, Andreas Färber <address@hidden> wrote:
>>> Am 13.03.2012 15:52, schrieb Zhi Yong Wu:
>>>> On Tue, Mar 13, 2012 at 10:36 PM, Andreas Färber <address@hidden> wrote:
>>>>> What you are looking for is the "parent" property which gets set up by
> [...adding a child property to some object. Many devices are not yet
> wired up as such...]
>>>> You mean that current device object should have one "parent" property?
>>>> Its parent device should have one "child" property pointing to it?
>>>> But i have not seen this property in qom-list output.
>>>> address@hidden qemu]# QMP/qom-list -s /tmp/server.sock /
>>>> vga/
>>>> i440fx/
>>>> peripheral/
>>>> peripheral-anon/
>>>
>>> Every one of these with */ is a child, in this case of the root "/". :)
>> Moreover, why can isa-serial device be liste in qom-list output but
>> kvmclock can't? where is the difference between their QOM?
>
> Because someone must give the child a name and assign a parent to it by
> calling said object_property_add_child(). ("wired up" above)
>
> Anthony had an RFC series refactoring i440fx, for instance, that sparked
> some controversy and was not followed-up yet.
thanks.
>
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg



-- 
Regards,

Zhi Yong Wu