From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, wenchaoqemu@gmail.com
Subject: Re: [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension
Date: Fri, 11 Jul 2014 09:38:26 -0600 [thread overview]
Message-ID: <53C004F2.1000602@redhat.com> (raw)
In-Reply-To: <87vbr4vtwp.fsf@blackfin.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]
On 07/11/2014 08:42 AM, Markus Armbruster wrote:
>>> Can anybody think of a use of c_var() that needs '.' preserved?
>>
>> Doing the replace in c_var() breaks some struct accesses in the generated
>> code. I didn't look deeper to determine the users though.
>
> Feels like a misuse of c_var() to me.
>
> Dig, dig... aha. generate_visit_struct_fields() joins QAPI names
> separated by '.', and passes the result to c_var(). I expect such code
> to break when one of the names contains '.'.
>
> It does indeed; try the appended patch to see it yourself. It generates
>
> struct VersionInfo
> {
> struct
> {
> int64_t major;
> int64_t minor;
> int64_t micro;
> } qemu;
Wait a minute. Isn't this one of the three cases of nested structs,
where we were already arguing that nested structs are evil if we are
going to introduce a fuller syntax for optional argument defaults?
> struct
> {
> int64_t major;
> int64_t minor;
> int64_t micro;
> } __com.redhat.crap;
> char *package;
> };
>
> Conclusion: this is simply a bug that needs fixing.
>
>
> diff --git a/qapi/common.json b/qapi/common.json
> index 4e9a21f..74ccde3 100644
> --- a/qapi/common.json
> +++ b/qapi/common.json
> @@ -52,6 +52,7 @@
> ##
> { 'type': 'VersionInfo',
> 'data': {'qemu': {'major': 'int', 'minor': 'int', 'micro': 'int'},
> + '__com.redhat.crap': {'major': 'int', 'minor': 'int', 'micro': 'int'},
> 'package': 'str'} }
And the fix may be as simple as ditching support for nested structs in
the first place, and rewriting this as:
{ 'type': 'VersionDetails',
'data': { major': 'int', 'minor': 'int', 'micro': 'int'} }
{ 'type': 'VersionInfo',
'data': {'qemu': 'VersionDetails',
'__com.redhat.crap': 'VersionDetails',
'package': 'str' } }
But the fact that we are still discussing makes it obvious - this is 2.2
material.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-11 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 18:17 [Qemu-devel] [PATCH] scripts: qapi-event.py: support vendor extension Luiz Capitulino
2014-07-09 15:43 ` [Qemu-devel] [PATCH for-2.1?] " Eric Blake
2014-07-09 16:08 ` Luiz Capitulino
2014-07-10 14:31 ` [Qemu-devel] [PATCH] " Markus Armbruster
2014-07-10 14:36 ` Luiz Capitulino
2014-07-11 14:42 ` Markus Armbruster
2014-07-11 15:38 ` Eric Blake [this message]
2014-07-11 16:01 ` Markus Armbruster
2014-07-11 18:51 ` Luiz Capitulino
2014-07-11 21:22 ` Eric Blake
2014-07-14 18:12 ` Luiz Capitulino
2014-07-14 18:31 ` Eric Blake
2014-07-14 18:32 ` Luiz Capitulino
2014-07-10 16:13 ` Eric Blake
2014-07-23 14:19 ` Wenchao Xia
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=53C004F2.1000602@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wenchaoqemu@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 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).