From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] about kvmclock QOM
Date: Tue, 13 Mar 2012 23:21:18 +0800 [thread overview]
Message-ID: <CAEH94Lj-hyMQw-ayDi17jUMOLdoQCePfdBLEWYYuv+whBXsVNg@mail.gmail.com> (raw)
In-Reply-To: <4F5F634E.8080507@suse.de>
On Tue, Mar 13, 2012 at 11:10 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 13.03.2012 15:52, schrieb Zhi Yong Wu:
>> On Tue, Mar 13, 2012 at 10:36 PM, Andreas Färber <afaerber@suse.de> wrote:
>>> What you are looking for is the "parent" property which gets set up by
>> 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?
>
> 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
next prev parent reply other threads:[~2012-03-13 15:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEH94Lj_+iEgXoMyzJu296NFm1R7hq1uOwAQrNd28khCctCKtQ@mail.gmail.com>
[not found] ` <4F5F4D4C.7010805@siemens.com>
[not found] ` <CAEH94Lhs4b07mf3dN5bQX-qUePRUN8DeUbppoCtGTgNDS_O=Ng@mail.gmail.com>
[not found] ` <4F5F5139.8080205@siemens.com>
2012-03-13 14:11 ` [Qemu-devel] about kvmclock QOM Zhi Yong Wu
2012-03-13 14:36 ` Andreas Färber
2012-03-13 14:52 ` Zhi Yong Wu
2012-03-13 15:10 ` Andreas Färber
2012-03-13 15:17 ` Zhi Yong Wu
2012-03-13 15:18 ` Andreas Färber
2012-03-13 15:24 ` Zhi Yong Wu
2012-03-13 15:21 ` Zhi Yong Wu [this message]
2012-03-13 16:28 ` Andreas Färber
2012-03-14 2:07 ` Zhi Yong Wu
2012-03-14 4:27 ` Gavin Shan
2012-03-14 5:23 ` Zhi Yong Wu
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=CAEH94Lj-hyMQw-ayDi17jUMOLdoQCePfdBLEWYYuv+whBXsVNg@mail.gmail.com \
--to=zwu.kernel@gmail.com \
--cc=afaerber@suse.de \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).