From: Paolo Bonzini <pbonzini@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com, qiaonuohan@cn.fujitsu.com,
xiawenc@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] full introspection support for QMP
Date: Fri, 20 Dec 2013 19:03:57 +0100 [thread overview]
Message-ID: <52B4868D.4010805@redhat.com> (raw)
In-Reply-To: <20131220115705.GD2890@amosk.info>
Il 20/12/2013 12:57, Amos Kong ha scritto:
> { 'type': 'DataObjectBase',
> 'data': { '*name': 'str', 'type': 'str' } }
> { 'union': 'DataObjectMemberType',
> 'discriminator': {},
> 'data': { 'reference': 'str',
> 'undefined': 'DataObject',
> 'extend': 'DataObject' } }
What is the purpose of "undefined"? I don't see any occurrence of any
of "undefined" or "extend" in the sample.
> { 'type': 'DataObjectMember',
> 'data': { 'type': 'DataObjectMemberType', '*name': 'str',
> '*optional': 'bool', '*recursive': 'bool' } }
> { 'type': 'DataObjectCommand',
> 'data': { '*data': [ 'DataObjectMember' ],
> '*returns': 'DataObject',
> '*gen': 'bool' } }
> { 'type': 'DataObjectEnumeration',
> 'data': { 'data': [ 'str' ] } }
> { 'type': 'DataObjectType',
> 'data': { 'data': [ 'DataObjectMember' ] } }
> { 'type': 'DataObjectUndefinedStruct',
Perhaps Unnamed or Anonymous?
> 'data': { 'data': [ 'DataObjectMember' ] } }
> { 'type': 'DataObjectUnion',
> 'data': { 'data': [ 'DataObjectMember' ], '*base': 'str',
> '*discriminator': 'str' } }
> { 'union': 'DataObject',
> 'base': 'DataObjectBase',
> 'discriminator': 'type',
> 'data': {
> 'command': 'DataObjectCommand',
> 'enumeration': 'DataObjectEnumeration',
> 'type': 'DataObjectType',
> 'undefined-struct': 'DataObjectUndefinedStruct',
> 'reference-type': 'String',
> 'unionobj': 'DataObjectUnion' } }
> { 'command': 'query-qmp-schema', 'returns': ['DataObject'] }
I think forcing expansion of everything that isn't unnamed/anonymous
makes the schema much larger and unwieldy. Otherwise looks great!
Paolo
next prev parent reply other threads:[~2013-12-20 18:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 10:37 [Qemu-devel] [PATCH v2 0/2] QMP full introspection Amos Kong
2013-07-16 10:37 ` [Qemu-devel] [PATCH v2 1/2] qapi: change qapi to convert schema json Amos Kong
2013-07-17 20:09 ` Luiz Capitulino
2013-07-26 3:39 ` Amos Kong
2013-07-19 12:27 ` Eric Blake
2013-07-26 6:53 ` Amos Kong
2013-07-16 10:37 ` [Qemu-devel] [PATCH v2 2/2] full introspection support for QMP Amos Kong
2013-07-16 10:48 ` Paolo Bonzini
2013-07-16 11:04 ` Amos Kong
2013-07-16 11:08 ` Paolo Bonzini
2013-07-16 12:04 ` Amos Kong
2013-07-16 12:18 ` Paolo Bonzini
2013-07-26 7:03 ` Amos Kong
2013-07-17 20:36 ` Luiz Capitulino
2013-07-19 20:26 ` Eric Blake
2013-07-26 7:21 ` Amos Kong
2013-07-19 22:05 ` Eric Blake
2013-07-26 7:51 ` Amos Kong
2013-07-26 11:52 ` Eric Blake
2013-11-27 2:32 ` Amos Kong
2013-11-27 9:51 ` Kevin Wolf
[not found] ` <20131220110001.GC2890@amosk.info>
2013-12-20 11:57 ` Amos Kong
2013-12-20 18:03 ` Paolo Bonzini [this message]
2013-12-23 8:11 ` Amos Kong
2013-12-23 6:32 ` Wenchao Xia
2013-12-23 7:15 ` 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=52B4868D.4010805@redhat.com \
--to=pbonzini@redhat.com \
--cc=akong@redhat.com \
--cc=kwolf@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 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.