From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35707) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7SqQ-0002kF-1W for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:37:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7SqI-00017I-HV for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:36:57 -0400 Received: from cantor2.suse.de ([195.135.220.15]:44459 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7SqI-00016N-8v for qemu-devel@nongnu.org; Tue, 13 Mar 2012 10:36:50 -0400 Message-ID: <4F5F5B80.6080609@suse.de> Date: Tue, 13 Mar 2012 15:36:48 +0100 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <4F5F4D4C.7010805@siemens.com> <4F5F5139.8080205@siemens.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] about kvmclock QOM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Zhi Yong Wu Cc: Jan Kiszka , QEMU Developers Am 13.03.2012 15:11, schrieb Zhi Yong Wu: > On Tue, Mar 13, 2012 at 9:52 PM, Jan Kiszka wr= ote: >> On 2012-03-13 14:40, Zhi Yong Wu wrote: >>> On Tue, Mar 13, 2012 at 9:36 PM, Jan Kiszka = wrote: >>>> On 2012-03-13 13:57, Zhi Yong Wu wrote: >>>>> HI, Jan >>>>> >>>>> Why can i not see kvmclock device in the output of qom-list? Since = it >>>>> has been converted to QOM. >>>> >>>> qom-list, like all QMP/ scripts, are currently broken for me, can't = test >>>> therefore. Please post any findings to the list while I'm digging in= to >>> I can see other devices such emulated nics via qom-list, but didn't >>> see kvmclock device in its output. >>> what is kvmclock's path if it can work normally? >>> My qemu command line is >>> >>> [root@f15 qemu]# x86_64-softmmu/qemu-system-x86_64 -m 512 -drive >>> file=3D/home/zwu/work/misc/image/rh6.1.img,if=3Dide,cache=3Dnone -ena= ble-kvm >>> -qmp unix:/tmp/server.sock,server,nowait -netdev type=3Duser,id=3Dnet >>> -device virtio-net-pci,netdev=3Dnet,id=3Dnet -net user,vlan=3D1 -devi= ce >>> virtio-net-pci,id=3Dnet2,vlan=3D1 -chardev id=3Dstdio,backend=3Dstdio= -device >>> isa-serial,chardev=3Dstdio,id=3Dserial >> >> Ah, now it works again (forgot mode=3D"control" for -mon). >> >>> >>> [root@f15 qemu]# QMP/qom-list -s /tmp/server.sock / >>> vga/ >>> i440fx/ >>> peripheral/ >>> peripheral-anon/ >>> [root@f15 qemu]# QMP/qom-list -s /tmp/server.sock /peripheral >>> serial/ >>> net2/ >>> net/ >>> >> >> kvmclock (like many devices) is not yet linked to some parent device, = so > static TypeInfo kvmclock_info =3D { > .name =3D "kvmclock", > .parent =3D TYPE_SYS_BUS_DEVICE, > It seems to be linked from here No. This specifies the parent class (base or super class). 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 and can only be inspected by info qtree monitor command. > .instance_size =3D sizeof(KVMClockState), > .class_init =3D kvmclock_class_init, > }; >=20 > I also checked other devices which can be seen in the output of > qom-list. I have not seen kvmclock QOM is different from other > devices. > So i am very surprised that why kvmclock device can not be seen in > qom-list output. >=20 >> it's not present in that tree. This also happens to auto-created >> isa-serial, e.g. (just leave out -device isa-serial) > Yeah, i can see it in qom-list output. Devices created by -device should be listed in the "/anon-peripheral" (or so) container. Check qom-list / for its child nodes. Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg