From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] [PULL 27/38] qmp: add new event "command-dropped"
Date: Fri, 16 Mar 2018 09:04:57 -0500 [thread overview]
Message-ID: <20180316140508.863778-28-eblake@redhat.com> (raw)
In-Reply-To: <20180316140508.863778-1-eblake@redhat.com>
This event will be emitted if one QMP command is dropped. Also,
declare an enum for the reasons.
Reviewed-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180309090006.10018-16-peterx@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
[eblake: rebase to master]
Signed-off-by: Eric Blake <eblake@redhat.com>
---
qapi/misc.json | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/qapi/misc.json b/qapi/misc.json
index 564216ae975..1545e416203 100644
--- a/qapi/misc.json
+++ b/qapi/misc.json
@@ -3390,3 +3390,40 @@
#
##
{ 'command': 'query-sev-capabilities', 'returns': 'SevCapability' }
+
+##
+# @CommandDropReason:
+#
+# Reasons that caused one command to be dropped.
+#
+# @queue-full: the command queue is full. This can only occur when
+# the client sends a new non-oob command before the
+# response to the previous non-oob command has been
+# received.
+#
+# Since: 2.12
+##
+{ 'enum': 'CommandDropReason',
+ 'data': [ 'queue-full' ] }
+
+##
+# @COMMAND_DROPPED:
+#
+# Emitted when a command is dropped due to some reason. Commands can
+# only be dropped when the oob capability is enabled.
+#
+# @id: The dropped command's "id" field.
+#
+# @reason: The reason why the command is dropped.
+#
+# Since: 2.12
+#
+# Example:
+#
+# { "event": "COMMAND_DROPPED",
+# "data": {"result": {"id": "libvirt-102",
+# "reason": "queue-full" } } }
+#
+##
+{ 'event': 'COMMAND_DROPPED' ,
+ 'data': { 'id': 'any', 'reason': 'CommandDropReason' } }
--
2.14.3
next prev parent reply other threads:[~2018-03-16 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:04 [Qemu-devel] [PULL 00/38] QAPI patches for 2018-03-12, 2.12 softfreeze Eric Blake
2018-03-16 14:04 ` [Qemu-devel] [PULL 07/38] qapi: Replace qobject_to_X(o) by qobject_to(X, o) Eric Blake
2018-03-16 14:04 ` [Qemu-devel] [PULL 12/38] chardev: tcp: postpone TLS work until machine done Eric Blake
2018-03-16 14:04 ` Eric Blake [this message]
2018-03-16 14:05 ` [Qemu-devel] [PULL 38/38] qapi: Pass '-u' when doing non-silent diff Eric Blake
2018-03-17 12:10 ` [Qemu-devel] [PULL 00/38] QAPI patches for 2018-03-12, 2.12 softfreeze Peter Maydell
2018-03-19 9:26 ` Peter Xu
2018-03-19 14:57 ` Eric Blake
2018-03-19 15:27 ` Eric Blake
2018-03-20 2:55 ` Peter Xu
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=20180316140508.863778-28-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=peterx@redhat.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).