diff options
| author | Markus Armbruster <armbru@redhat.com> | 2021-10-28 12:25:20 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2021-10-29 21:28:01 +0200 |
| commit | 57df0dff1a1f4c846aa74a082bfd595a8a990015 (patch) | |
| tree | d5953753c4ec81c9f153ea9ce6fe1370b33c7c1b /hw | |
| parent | 7ce5fc63c75d0ac756fd0b4d0472774de17f8fec (diff) | |
| download | qemu-57df0dff1a1f4c846aa74a082bfd595a8a990015.zip qemu-57df0dff1a1f4c846aa74a082bfd595a8a990015.tar.gz qemu-57df0dff1a1f4c846aa74a082bfd595a8a990015.tar.bz2 | |
qapi: Extend -compat to set policy for unstable interfaces
New option parameters unstable-input and unstable-output set policy
for unstable interfaces just like deprecated-input and
deprecated-output set policy for deprecated interfaces (see commit
6dd75472d5 "qemu-options: New -compat to set policy for deprecated
interfaces"). This is intended for testing users of the management
interfaces. It is experimental.
For now, this covers only syntactic aspects of QMP, i.e. stuff tagged
with feature 'unstable'. We may want to extend it to cover semantic
aspects, or the command line.
Note that there is no good way for management application to detect
presence of these new option parameters: they are not visible output
of query-qmp-schema or query-command-line-options. Tolerable, because
it's meant for testing. If running with -compat fails, skip the test.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Acked-by: John Snow <jsnow@redhat.com>
Message-Id: <20211028102520.747396-10-armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[Doc comments fixed up]
Diffstat (limited to 'hw')
0 files changed, 0 insertions, 0 deletions