qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [RFC 0/3] qmp: Return extra information on qom-list-types
Date: Fri, 19 May 2017 23:09:11 -0300	[thread overview]
Message-ID: <20170520020914.14562-1-ehabkost@redhat.com> (raw)

This series adds 'abstract' and 'parent-types' fields to the
output of qom-list-types.

For reference, below are the sizes of the output of
"qom-list-types abstract=true" on qemu-system-x86_64, before and
after applying the patches:

* before: 11724 bytes
* with 'abstract' field: 20119 bytes
* with 'abstract' and 'parent-types': 44383 bytes

I'm not sure if extending qom-list-types with this info is the
right way to go, or if we should keep qom-list-types as-is and
add a new "query-qom-type" QMP command to query info on one QOM
type at a time.

Eduardo Habkost (3):
  tests: Simplify abstract-interfaces check with a helper
  qmp: Include 'abstract' field on 'qom-list-types' output
  qmp: Include parent types on 'qom-list-types' output

 qapi-schema.json               |   9 ++-
 qmp.c                          |  17 ++++++
 tests/device-introspect-test.c | 131 ++++++++++++++++++++++++++++++++---------
 3 files changed, 127 insertions(+), 30 deletions(-)

-- 
2.11.0.259.g40922b1

             reply	other threads:[~2017-05-20  2:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20  2:09 Eduardo Habkost [this message]
2017-05-20  2:09 ` [Qemu-devel] [RFC 1/3] tests: Simplify abstract-interfaces check with a helper Eduardo Habkost
2017-05-20  2:09 ` [Qemu-devel] [RFC 2/3] qmp: Include 'abstract' field on 'qom-list-types' output Eduardo Habkost
2017-05-20  2:09 ` [Qemu-devel] [RFC 3/3] qmp: Include parent types " Eduardo Habkost
2017-05-23 14:12 ` [Qemu-devel] [RFC 0/3] qmp: Return extra information on qom-list-types Markus Armbruster
2017-05-23 14:34   ` Eduardo Habkost
2017-05-24 12:13     ` Markus Armbruster
2017-05-24 13:13       ` Eduardo Habkost
2017-05-24 14:31       ` Eric Blake

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=20170520020914.14562-1-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.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).