Hi Eduardo,
On 04/23/2019 06:22 PM, Eduardo Habkost wrote:
This struct will be used to represent support and deprecation
status of QEMU features.
Signed-off-by: Eduardo Habkost <ehabk...@redhat.com>
---
qapi/common.json | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/qapi/common.json b/qapi/common.json
index 99d313ef3b..b59d0dc66b 100644
--- a/qapi/common.json
+++ b/qapi/common.json
@@ -193,3 +193,27 @@
'ppc64', 'riscv32', 'riscv64', 's390x', 'sh4',
'sh4eb', 'sparc', 'sparc64', 'tricore', 'unicore32',
'x86_64', 'xtensa', 'xtensaeb' ] }
+
+##
+# @SupportStatusInfo:
+#
+# Information on support status of a given feature
+# (e.g. machine type)
+#
+# @deprecated: if true, the given feature is deprecated and may be removed
+# in future versions of QEMU according to the QEMU deprecation
+# policy.
Eventually management software will need the know the QEMU version the
feature is planed for removal. So makes sense to include a field to
capture that information as well or do you expect it to be added (as a
good practice) in the 'status-message'?
- Wainer
+#
+# @status-message: Human readable message describing support status
+# of the feature.
+#
+# @suggested-alternative: Optional. Suggested alternative for a deprecated
+# feature. For machine types, this should be the name
+# of an available machine-type.
+#
+# Since: 4.1
+##
+{ 'struct': 'SupportStatusInfo',
+ 'data': { 'deprecated': 'bool',
+ '*status-message': 'str',
+ '*suggested-alternative': 'str' } }
