From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Ricardo Perez Blanco <ricardo.perez_blanco@nokia.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] Show values and description when using "qom-list"
Date: Fri, 8 Jun 2018 10:41:01 +0100 [thread overview]
Message-ID: <20180608094101.GG2671@work-vm> (raw)
In-Reply-To: <a51fbf8b-9839-ebc1-cde5-5ae95656f918@suse.de>
* Andreas Färber (afaerber@suse.de) wrote:
> Am 01.06.2018 um 17:39 schrieb Ricardo Perez Blanco:
> > For debugging purposes it is very useful to:
> > - See the description of the field. This information is already filled
> > in but not shown in "qom-list" command.
>
> No objection on this part.
>
> > - Display value of the field.
>
> That is by definition the qom-get operation, not qom-list. Just like the
> ls command does not show file contents, there's cat etc. for that. For
> debugging purposes we had a qom-tree (?) command that would combine
> both.
I'm not too bothered about distinguishing between the two commands;
but it would be nice - one reason I'm not too bothered is because we've
failed to get a qom-get in multiple years of trying.
> There might be unmerged patches on qemu-devel related to display
> of certain data types.
Which ones?
Dave
> Regards,
> Andreas
>
> >
> > Signed-off-by: Ricardo Perez Blanco <ricardo.perez_blanco@nokia.com>
> > ---
> > hmp.c | 13 +++++++++++--
> > qapi/misc.json | 6 ++++--
> > qmp.c | 7 +++++++
> > qom/object.c | 8 +++-----
> > 4 files changed, 25 insertions(+), 9 deletions(-)
> [snip]
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg)
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-06-08 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 15:39 [Qemu-devel] [PATCH v2] Show values and description when using "qom-list" Ricardo Perez Blanco
2018-06-01 16:01 ` Eric Blake
2018-06-11 7:18 ` Perez Blanco, Ricardo (Nokia - BE/Antwerp)
2018-06-02 7:20 ` Andreas Färber
2018-06-08 9:41 ` Dr. David Alan Gilbert [this message]
2018-06-08 16:19 ` Andreas Färber
2018-06-11 7:17 ` Perez Blanco, Ricardo (Nokia - BE/Antwerp)
2018-06-12 6:02 ` Markus Armbruster
2018-06-25 11:32 ` Markus Armbruster
2018-06-25 15:00 ` Dr. David Alan Gilbert
2018-06-25 18:42 ` Markus Armbruster
2018-06-29 12:17 ` Dr. David Alan Gilbert
2018-06-29 12:39 ` Perez Blanco, Ricardo (Nokia - BE/Antwerp)
2018-07-02 6:36 ` Markus Armbruster
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=20180608094101.GG2671@work-vm \
--to=dgilbert@redhat.com \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ricardo.perez_blanco@nokia.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 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).