From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] input: improve docs for input-send-event qmp command
Date: Fri, 21 Nov 2014 15:53:06 +0100 [thread overview]
Message-ID: <1416581586.3856.8.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <87fvdczrvl.fsf@blackfin.pond.sub.org>
On Fr, 2014-11-21 at 12:59 +0100, Markus Armbruster wrote:
> [Copying Eric]
>
> Gerd Hoffmann <kraxel@redhat.com> writes:
>
> > Text partly suggested by Markus Armbruster <armbru@redhat.com>
> >
> > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > ---
> > qapi-schema.json | 12 ++++++++++++
> > 1 file changed, 12 insertions(+)
> >
> > diff --git a/qapi-schema.json b/qapi-schema.json
> > index d0926d9..fcd49b1 100644
> > --- a/qapi-schema.json
> > +++ b/qapi-schema.json
> > @@ -3250,6 +3250,18 @@
> > # Send input event(s) to guest.
> > #
> > # @console: #optional console to send event(s) to.
> > +# This parameter can be used to send the input event to
> > +# specific input devices in case (a) multiple input devices
> > +# of the same kind are added to the virtual machine and (b)
> > +# you have configured input routing (see docs/multiseat.txt)
> > +# for those input devices. If input routing is not
> > +# configured this parameter has no effect.
> > +# 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 take precedence.
> > +
> > #
> > # @events: List of InputEvent union.
> > #
>
> What is a "console", and how get input devices assoated with one? I
> checked docs/multiseat.txt for clues, but found none.
Oh, right, in the command line the video device names are used. video
device emulation actually creates the consoles, typically console 0 is
your vga. They are numbered in creation order. You can inspect them in
the qom tree (/backend/console[$nr]). There is a device link pointing
to the device which created it.
cheers,
Gerd
next prev parent reply other threads:[~2014-11-21 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 9:30 [Qemu-devel] [PATCH] input: improve docs for input-send-event qmp command Gerd Hoffmann
2014-11-21 11:59 ` Markus Armbruster
2014-11-21 14:53 ` Gerd Hoffmann [this message]
2014-11-24 14:08 ` Markus Armbruster
2014-11-24 14:37 ` Gerd Hoffmann
2014-11-24 15:51 ` Markus Armbruster
2014-11-24 16:47 ` Eric Blake
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=1416581586.3856.8.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@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).