diff mbox series

[3/4] qapi/machine.json: add DEVICE_UNPLUG_ERROR QAPI event

Message ID 20210312200740.815014-4-danielhb413@gmail.com (mailing list archive)
State New, archived
Headers show
Series DEVICE_NOT_DELETED/DEVICE_UNPLUG_ERROR QAPI events | expand

Commit Message

Daniel Henrique Barboza March 12, 2021, 8:07 p.m. UTC 
At this moment we only provide one event to report a hotunplug error,
MEM_UNPLUG_ERROR. There will be other device types that are going to be
throwing unplug errors in the future though.

Instead of creating a (device_type)_UNPLUG_ERROR for each new device,
create a generic DEVICE_UNPLUG_ERROR event that can be used by all
unplug errors in the future.

Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
---
 qapi/machine.json | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
diff mbox series

Patch

diff --git a/qapi/machine.json b/qapi/machine.json
index 330189efe3..9b2c93aad3 100644
--- a/qapi/machine.json
+++ b/qapi/machine.json
@@ -1471,3 +1471,26 @@ 
 ##
 { 'event': 'MEM_UNPLUG_ERROR',
   'data': { 'device': 'str', 'msg': 'str' } }
+
+##
+# @DEVICE_UNPLUG_ERROR:
+#
+# Emitted when a device hot unplug error occurs.
+#
+# @device: device name
+#
+# @msg: Informative message
+#
+# Since: 6.0
+#
+# Example:
+#
+# <- { "event": "DEVICE_UNPLUG_ERROR"
+#      "data": { "device": "dimm1",
+#                "msg": "Memory hotunplug rejected by the guest for device dimm1"
+#      },
+#      "timestamp": { "seconds": 1615570772, "microseconds": 202844 } }
+#
+##
+{ 'event': 'DEVICE_UNPLUG_ERROR',
+  'data': { 'device': 'str', 'msg': 'str' } }
\ No newline at end of file