Re: [Qemu-devel] about kvmclock QOM

[Gavin Shan <shangw@linux.vnet.ibm.com>]

> >>>>> 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.
> >>>> [root@f15 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.

I'm a little curious that QOM will become more dependent than ever. Originally,
qemu has qdev prototype to trace device/bus staff. Is QOM going to replace qdev/qbus
staff in future?

Thanks,
Gavin