From: John Snow <jsnow@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Sample 'qapi-schema-diff' output for v9.0.0 vs origin/master
Date: Thu, 13 Jun 2024 10:07:56 -0400 [thread overview]
Message-ID: <CAFn=p-bhiN1ig1t++6FWNc5waYdGvgr_iL3TSHOSUcmwO9GDpA@mail.gmail.com> (raw)
In-Reply-To: <c826b3dc-2a49-493f-8e6d-efffbfc74f70@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2447 bytes --]
On Thu, Jun 13, 2024, 4:50 AM Philippe Mathieu-Daudé <philmd@linaro.org>
wrote:
> Hi John,
>
Hi Phil!
> On 12/6/24 20:40, John Snow wrote:
> > Hiya, here's some draft output of a script I'm working on to summarize
> > QMP wire format differences between QEMU versions.
> >
> > This script works in terms of the QMP *wire format*, not the QAPI
> > *specification*. As a consequence, *almost* all type names are stripped
> > from this output and all nested structures are fully inlined - so
> > changes to shared data structures, enums, etc will manifest as many
> > independent changes. Similarly, changes to type names and type
> > factorings that do not change the wire format will not appear in this
> > report at all.
>
> Do you include changes on unstable features or are you skipping them?
>
> Possible feature request: skip them by default until a --unstable
> CLI option is used.
>
In this early draft, I do include such changes. I might want to /opt-in/ to
hiding them (maybe: --hide-unstable), but it can be done.
(A summary mode that hides itemized changes may also be useful for
observing broad-changes-at-a-glance and might be worth adding, too.
--no-detail or --brief or some such.)
I assume we want to hide anything that has the unstable feature flag at the
command *root* and any command or event named with the x- prefix. (unstable
fields on stable commands ... tbd.)
I still need to implement full support for if/features, so this idea can
come along for the ride when I flesh out those details.
(features/if for top-level definitions are recorded, but are likely missing
for various nested fields. The diff output will remark on what changed on
the summary line where it says "(arguments)" or "(arguments, returns)" with
the tokens "if" or "features", but it doesn't break it out into discrete
elements like everything else does, yet - and it still likely only catches
those differences when they occur at the definition root.)
> >
> > This is still a WIP: if conditionals and features may not be fully
> > represented in this summary report.
>
> Regards,
>
> Phil.
>
Thanks for the suggestion!
BTW, I sent a new mail out to the list with a link to gitlab for source and
sample output for this tool and other goodies; the URL is
https://gitlab.com/jsnow/externalized-qapi - see the other mail for details
on what's in here, if curious.
--js
>
[-- Attachment #2: Type: text/html, Size: 3910 bytes --]
next prev parent reply other threads:[~2024-06-13 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 18:40 Sample 'qapi-schema-diff' output for v9.0.0 vs origin/master John Snow
2024-06-13 8:49 ` Philippe Mathieu-Daudé
2024-06-13 14:07 ` John Snow [this message]
2024-06-13 14:54 ` Daniel P. Berrangé
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='CAFn=p-bhiN1ig1t++6FWNc5waYdGvgr_iL3TSHOSUcmwO9GDpA@mail.gmail.com' \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=philmd@linaro.org \
--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).