qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org, kraxel@redhat.com
Cc: mtosatti@redhat.com, armbru@redhat.com, lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH for-2.2] qmp: document input-send-event detail
Date: Mon, 24 Nov 2014 22:46:11 +0800	[thread overview]
Message-ID: <1416840371-27646-1-git-send-email-akong@redhat.com> (raw)

This patch documents what exactly input-send-event is supposed to do.

Signed-off-by: Amos Kong <akong@redhat.com>
---
 qapi-schema.json | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/qapi-schema.json b/qapi-schema.json
index d0926d9..9aa19bc 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -3249,7 +3249,18 @@
 #
 # Send input event(s) to guest.
 #
+# The VM must be running or suspended.
+#
+# Each event is sent to exactly one admissible input device. Such a
+# device must exist. If multiple admissible devices can handle an
+# event, which one gets it is unspecified, except as described below.
+#
 # @console: #optional console to send event(s) to.
+#           If @console is missing, only devices that aren't associated
+#           with a console are admissible.
+#           If @console is specified, it must exist, and both devices
+#           associated with that console and devices not associated with a
+#           console are admissible, but the former takes precedence.
 #
 # @events: List of InputEvent union.
 #
-- 
1.9.3

             reply	other threads:[~2014-11-24 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:46 Amos Kong [this message]
2014-11-24 15:39 ` [Qemu-devel] [PATCH for-2.2] qmp: document input-send-event detail Markus Armbruster

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=1416840371-27646-1-git-send-email-akong@redhat.com \
    --to=akong@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mtosatti@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).