From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: qiaonuohan@cn.fujitsu.com, lcapitulino@redhat.com,
mdroth@linux.vnet.ibm.com, xiawenc@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v4 0/5] QMP full introspection
Date: Thu, 23 Jan 2014 22:46:31 +0800 [thread overview]
Message-ID: <1390488396-16538-1-git-send-email-akong@redhat.com> (raw)
This is an implement of qmp full-introspection,
parse and convert the json schema to a dynamical tree,
return it to management through QMP command output.
The whole output of query-qmp-schema command:
http://i-kvm.rhcloud.com/static/pub/v4/qmp-introspection.output.txt
http://i-kvm.rhcloud.com/static/pub/v4/qmp-introspection.h
Welcome your comments!
V2: use 'DataObject' to describe dynamic struct
V3: improve the metadata as suggested by eric
V4: use python to extend/parse schema for improving
the response speed and simple the code
Amos Kong (5):
qapi: introduce DataObject to describe dynamic structs
qapi: add qapi-introspect.py code generator
qobject: introduce qobject_get_str()
qmp: full introspection support for QMP
update docs/qmp-full-introspection.txt
.gitignore | 1 +
Makefile | 5 +-
docs/qmp-full-introspection.txt | 99 ++++++++++++++++++
include/qapi/qmp/qstring.h | 1 +
qapi-schema.json | 152 ++++++++++++++++++++++++++++
qmp-commands.hx | 42 ++++++++
qmp.c | 215 ++++++++++++++++++++++++++++++++++++++++
qobject/qstring.c | 19 ++++
scripts/qapi-introspect.py | 172 ++++++++++++++++++++++++++++++++
9 files changed, 705 insertions(+), 1 deletion(-)
create mode 100644 docs/qmp-full-introspection.txt
create mode 100644 scripts/qapi-introspect.py
--
1.8.4.2
next reply other threads:[~2014-01-23 14:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 14:46 Amos Kong [this message]
2014-01-23 14:46 ` [Qemu-devel] [PATCH v4 1/5] qapi: introduce DataObject to describe dynamic structs Amos Kong
2014-02-03 19:56 ` Eric Blake
2014-01-23 14:46 ` [Qemu-devel] [PATCH v4 2/5] qapi: add qapi-introspect.py code generator Amos Kong
2014-01-24 9:12 ` Fam Zheng
2014-01-24 9:34 ` Amos Kong
2014-01-26 4:51 ` Amos Kong
2014-02-04 0:15 ` Eric Blake
2014-02-11 0:35 ` Eric Blake
2014-01-23 14:46 ` [Qemu-devel] [PATCH v4 3/5] qobject: introduce qobject_get_str() Amos Kong
2014-02-04 0:20 ` Eric Blake
2014-01-23 14:46 ` [Qemu-devel] [PATCH v4 4/5] qmp: full introspection support for QMP Amos Kong
2014-01-24 10:48 ` Fam Zheng
2014-01-27 8:17 ` Amos Kong
2014-01-27 8:50 ` Amos Kong
2014-01-27 9:38 ` Paolo Bonzini
2014-01-27 10:07 ` Amos Kong
2014-01-27 10:15 ` Paolo Bonzini
2014-01-27 10:46 ` Fam Zheng
2014-01-28 10:45 ` Amos Kong
2014-01-28 11:14 ` Paolo Bonzini
2014-01-28 13:58 ` Eric Blake
2014-01-29 8:12 ` Fam Zheng
2014-02-04 0:33 ` Eric Blake
2014-01-23 14:46 ` [Qemu-devel] [PATCH v4 5/5] update docs/qmp-full-introspection.txt Amos Kong
2014-01-24 11:43 ` Paolo Bonzini
2014-01-24 13:07 ` Eric Blake
2014-01-24 8:42 ` [Qemu-devel] [PATCH v4 0/5] QMP full introspection Amos Kong
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=1390488396-16538-1-git-send-email-akong@redhat.com \
--to=akong@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaonuohan@cn.fujitsu.com \
--cc=xiawenc@linux.vnet.ibm.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).