From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35287) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7foX-0005td-V0 for qemu-devel@nongnu.org; Wed, 14 Mar 2012 00:28:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7foU-0003xm-65 for qemu-devel@nongnu.org; Wed, 14 Mar 2012 00:27:53 -0400 Received: from e28smtp05.in.ibm.com ([122.248.162.5]:32903) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7foT-0003wD-Ct for qemu-devel@nongnu.org; Wed, 14 Mar 2012 00:27:50 -0400 Received: from /spool/local by e28smtp05.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 14 Mar 2012 09:57:39 +0530 Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay01.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q2E4RYlh3854434 for ; Wed, 14 Mar 2012 09:57:35 +0530 Received: from d28av01.in.ibm.com (loopback [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q2E9vK54029156 for ; Wed, 14 Mar 2012 15:27:20 +0530 Date: Wed, 14 Mar 2012 12:27:31 +0800 From: Gavin Shan Message-ID: <20120314042731.GA21794@shangw> References: <4F5F4D4C.7010805@siemens.com> <4F5F5139.8080205@siemens.com> <4F5F5B80.6080609@suse.de> <4F5F634E.8080507@suse.de> <4F5F75A6.70905@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] about kvmclock QOM Reply-To: Gavin Shan List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Zhi Yong Wu Cc: Jan Kiszka , QEMU Developers , Anthony Liguori > >>>>> 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