From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael Roth" <michael.roth@amd.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: [PATCH 0/3] audio: make audiodev introspectable by mgmt apps
Date: Tue, 2 Mar 2021 17:55:21 +0000 [thread overview]
Message-ID: <20210302175524.1290840-1-berrange@redhat.com> (raw)
The Audiodev QAPI type is not introspectable via query-qmp-schema as
nothing in QEMU uses it. -audiodev is not introspectable via
query-command-line-options because it avoided legacy QemuOpts
Even once that is fixed, the introspection lies about what is
actually possible because nearly all the audio backends are compile
time conditional, but the QAPI schema is fixed.
The last patch is a trivial addition that aided my debugging while
investigating the problems and not directly related/dependant.
Daniel P. Berrangé (3):
qapi, audio: add query-audiodev command
qapi, audio: respect build time conditions in audio schema
qapi: provide a friendly string representation of QAPI classes
audio/audio.c | 35 ++++++++++++++++++++++++++
audio/audio_legacy.c | 41 +++++++++++++++++++++++++++++-
audio/audio_template.h | 16 ++++++++++++
qapi/audio.json | 57 ++++++++++++++++++++++++++++++++++--------
scripts/qapi/schema.py | 3 +++
5 files changed, 141 insertions(+), 11 deletions(-)
--
2.29.2
next reply other threads:[~2021-03-02 17:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 17:55 Daniel P. Berrangé [this message]
2021-03-02 17:55 ` [PATCH 1/3] qapi, audio: add query-audiodev command Daniel P. Berrangé
2021-03-02 19:03 ` Eric Blake
2021-03-02 21:10 ` Philippe Mathieu-Daudé
2021-03-02 21:12 ` Philippe Mathieu-Daudé
2021-03-03 10:07 ` Daniel P. Berrangé
2021-03-03 10:08 ` Daniel P. Berrangé
2021-03-05 13:01 ` Markus Armbruster
2021-03-11 11:00 ` Daniel P. Berrangé
2021-03-02 17:55 ` [PATCH 2/3] qapi, audio: respect build time conditions in audio schema Daniel P. Berrangé
2021-03-02 19:05 ` Eric Blake
2021-03-03 10:09 ` Daniel P. Berrangé
2021-03-03 7:00 ` Gerd Hoffmann
2021-03-03 10:11 ` Daniel P. Berrangé
2021-03-05 10:56 ` Markus Armbruster
2021-03-11 11:04 ` Daniel P. Berrangé
2021-03-05 12:12 ` Markus Armbruster
2022-12-12 16:53 ` Thomas Huth
2022-12-14 11:28 ` Daniel P. Berrangé
2021-03-02 17:55 ` [PATCH 3/3] qapi: provide a friendly string representation of QAPI classes Daniel P. Berrangé
2021-03-02 19:06 ` Eric Blake
2021-03-02 21:02 ` Philippe Mathieu-Daudé
2021-03-05 13:18 ` Markus Armbruster
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=20210302175524.1290840-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=michael.roth@amd.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).