From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Peter Krempa" <pkrempa@redhat.com>,
"Daniil Tatianin" <d-tatianin@yandex-team.ru>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
qemu-devel@nongnu.org, devel@lists.libvirt.org,
"Michal Privoznik" <mprivozn@redhat.com>
Subject: Re: -chardev with a JSON argument (was: [PATCH] chardev: introduce 'reconnect-ms' and deprecate 'reconnect')
Date: Mon, 16 Sep 2024 12:30:36 +0200 [thread overview]
Message-ID: <ZugIzLK6UKkRRw-1@redhat.com> (raw)
In-Reply-To: <87a5gavd6r.fsf_-_@pond.sub.org>
Am 14.09.2024 um 10:42 hat Markus Armbruster geschrieben:
> Peter Krempa <pkrempa@redhat.com> writes:
>
> > This is a little off-topic:
> >
> > So I wanted to make libvirt use the new parameter to stay ahead
> > deprecation. I've applied this patch to qemu, dumped capabilities and
> > pretty much expected a bunch of test cases in libvirt fail as they'd be
> > using a deprecated field as libvirt is supposed to validate everything.
> >
> > And the test suite passed unexpectedly. I've dug further and noticed
> > that for some reason libvirt doesn't still use JSON parameters for
> > -chardev (which is the pre-requisite for validation).
> >
> > I've also noticed that at some point I attempted to convert it over
> > witnessed by having an (unused) capability named QEMU_CAPS_CHARDEV_JSON
> > that I've introduced.
> >
> > My questions are:
> > 1) Does '-chardev' accept JSON identical to 'chardev-add' QMP command?
>
> Sadly, no.
>
> How badly do you want it?
I suppose even my old patches to fully QAPIfy -chardev could be revived,
which would not only add JSON support, but also make sure that
everything that works in JSON also works with keyval syntax, both ways
stay in sync in the future and that you can access non-scalar options
without JSON:
https://repo.or.cz/qemu/kevin.git/shortlog/refs/tags/qapi-alias-chardev-v4
Without QAPI aliases, they will have to contain some ugly code to do the
compatibility conversion, but whatever can be generated can also be
written manually...
Kevin
next prev parent reply other threads:[~2024-09-16 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 5:19 [PATCH] chardev: introduce 'reconnect-ms' and deprecate 'reconnect' Daniil Tatianin
2024-09-04 9:00 ` Vladimir Sementsov-Ogievskiy
2024-09-04 11:21 ` Peter Krempa
2024-09-14 8:42 ` -chardev with a JSON argument (was: [PATCH] chardev: introduce 'reconnect-ms' and deprecate 'reconnect') Markus Armbruster
2024-09-16 6:26 ` Peter Krempa
2024-09-16 10:30 ` Kevin Wolf [this message]
2024-09-05 8:02 ` [PATCH] chardev: introduce 'reconnect-ms' and deprecate 'reconnect' Paolo Bonzini
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=ZugIzLK6UKkRRw-1@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=d-tatianin@yandex-team.ru \
--cc=devel@lists.libvirt.org \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@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).