@@ -453,6 +453,10 @@
# @extents: The "Extent List" field as defined in Compute Express Link
# (CXL) Specification, Revision 3.1, Table 7-70.
#
+# Features:
+#
+# @unstable: For now this command is subject to change.
+#
# Since : 9.1
##
{ 'command': 'cxl-add-dynamic-capacity',
@@ -462,7 +466,8 @@
'region': 'uint8',
'*tag': 'str',
'extents': [ 'CxlDynamicCapacityExtent' ]
- }
+ },
+ 'features': [ 'unstable' ]
}
##
@@ -527,6 +532,10 @@
# @extents: The "Extent List" field as defined in Compute Express
# Link (CXL) Specification, Revision 3.1, Table 7-71.
#
+# Features:
+#
+# @unstable: For now this command is subject to change.
+#
# Since : 9.1
##
{ 'command': 'cxl-release-dynamic-capacity',
@@ -538,5 +547,6 @@
'region': 'uint8',
'*tag': 'str',
'extents': [ 'CxlDynamicCapacityExtent' ]
- }
+ },
+ 'features': [ 'unstable' ]
}
Markus suggested that we make the unstable. I don't expect these interfaces to change because of their tight coupling to the Compute Express Link (CXL) Specification, Revision 3.1 Fabric Management API definitions which can only be extended in backwards compatible way. However, there seems little disadvantage in taking a cautious path for now and marking them as unstable interfaces. Suggested-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> --- qapi/cxl.json | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-)