From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"John Snow" <jsnow@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: QAPI sync meeting
Date: Thu, 7 Oct 2021 12:23:58 +0200 [thread overview]
Message-ID: <3abc4e8e-5657-14bb-ba89-5b7669c01201@redhat.com> (raw)
In-Reply-To: <YV7Fh2DihM65rgnN@redhat.com>
On 07/10/21 12:01, Kevin Wolf wrote:
>
> * -chardev: I have patches that QAPIfy the option based on aliases,
> getting rid of the old handwritten parser that is inconsistent with
> QMP in non-obvious ways and replacing it with translation to QMP
> (both using aliases and a little C code) that makes the differences
> obvious.
>
> First posted in November 2020, more details in the cover letter:
> https://patchew.org/QEMU/20201112175905.404472-1-kwolf@redhat.com/
>
> Later versions (not yet posted as a series because I'm waiting for
> aliases) also make -chardev accept JSON syntax, which is what
> libvirt really wants to use.
I'm still not sure about this... It's an awful lot of code if the
aliases are only used by -chardev, and I'd rather use -object/object-add
for chardevs if that's at all possible.
Paolo
next prev parent reply other threads:[~2021-10-07 10:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 16:55 QAPI sync meeting John Snow
2021-09-28 11:38 ` Marc-André Lureau
2021-09-28 13:14 ` Kevin Wolf
2021-09-28 13:53 ` Daniel P. Berrangé
2021-09-28 17:43 ` John Snow
2021-09-29 12:18 ` Markus Armbruster
2021-09-30 0:49 ` John Snow
2021-10-07 10:01 ` Kevin Wolf
2021-10-07 10:23 ` Paolo Bonzini [this message]
2021-10-07 12:53 ` Kevin Wolf
2021-10-07 13:02 ` Daniel P. Berrangé
2021-10-08 10:06 ` Markus Armbruster
2021-10-08 17:07 ` Paolo Bonzini
2021-10-07 12:43 ` John Snow
2021-09-28 15:19 ` Paolo Bonzini
2021-09-29 13:42 ` Damien Hedde
2021-09-30 0:31 ` John Snow
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=3abc4e8e-5657-14bb-ba89-5b7669c01201@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@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 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.