From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: QingFeng Hao <haoqf@linux.vnet.ibm.com>
Cc: qemu block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] Why is there no qom_get in hmp.c?
Date: Wed, 18 Apr 2018 15:04:59 +0100 [thread overview]
Message-ID: <20180418140458.GA2723@work-vm> (raw)
In-Reply-To: <16124cce-593c-8191-074c-19164acc3626@linux.vnet.ibm.com>
* QingFeng Hao (haoqf@linux.vnet.ibm.com) wrote:
> Hi all,
> I did some investigation and found that "virsh qemu-monitor-command" supports qom-get,
> but qemu hmp doesn't. However, in hmp.c there are qom_list and qom_set. It confused me
> and my question is: why is this? And how can I get a property's value in hmp? e.g.
> qemu-system-* -nodefaults -machine accel=qtest -no-shutdown -nographic -monitor stdio -serial none -hda /root/t.qcow2
> "info qtree" can only get a few properties.
I did try that in 2016 (see my series from about September); but it got
bogged down in trying to fix output visitors; it's possible the visitor
code has been fixed since then though.
The 'Show values and description when using "qom-list"' patch
that Ricardo Perez Blanco posted would do something similar.
Dave
> Thanks a lot!
> --
> Regards
> QingFeng Hao
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-04-18 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:51 [Qemu-devel] Why is there no qom_get in hmp.c? QingFeng Hao
2018-04-18 14:04 ` Dr. David Alan Gilbert [this message]
2018-04-19 3:27 ` QingFeng Hao
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=20180418140458.GA2723@work-vm \
--to=dgilbert@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=haoqf@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.