From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: spice-devel <spice-devel@lists.freedesktop.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [Spice-devel] paravirtual mouse/tablet
Date: Thu, 13 Jan 2011 12:51:50 +0100 [thread overview]
Message-ID: <4D2EE756.2020808@redhat.com> (raw)
In-Reply-To: <AANLkTikECZUmQKQpmRPQv5QcOs=oKJG_E0ySQBxnWpU3@mail.gmail.com>
On 01/13/11 12:01, Stefan Hajnoczi wrote:
> Can you elaborate how the spice display channel comes into play? On a
> physical machine you just have input devices with no notion of
> display. It's up to the windowing system to process input events and
> handle multihead. Why does a pv tablet tie itself to a display
> channel?
You have two qxl devices, each linked to a spice display channel. The
spice client will open one window for each channel. The mouse position
is a triple consisting of (x, y, window/channel).
Only the guest knows how it configured the displays, so only the guest
is able to create a correct pointer position out of this data. So the
X-Server would combine this data with its virtual display configuration
(basically adding the display offset to the coordinates), then send this
as event to the X clients.
> What about mouse wheel (aka z axis motion)?
It's covered. That are really just button presses at mouse protocol
level (buttons 4+5). We can add them to the enum to have fancy names
for them, that is just the sugar on top though.
cheers,
Gerd
next prev parent reply other threads:[~2011-01-13 11:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 10:19 [Qemu-devel] paravirtual mouse/tablet Gerd Hoffmann
2011-01-13 11:01 ` [Qemu-devel] Re: [Spice-devel] " Stefan Hajnoczi
2011-01-13 11:51 ` Gerd Hoffmann [this message]
2011-01-13 15:55 ` Anthony Liguori
2011-01-13 17:08 ` Gerd Hoffmann
2011-01-13 20:41 ` Anthony Liguori
2011-01-14 8:49 ` Gerd Hoffmann
2011-01-14 10:48 ` Daniel P. Berrange
2011-01-14 14:14 ` Anthony Liguori
2011-01-14 14:28 ` Alon Levy
2011-01-14 14:52 ` Daniel P. Berrange
2011-01-14 16:10 ` [Spice-devel] [Qemu-devel] " Alon Levy
2011-01-13 15:52 ` [Qemu-devel] " Anthony Liguori
2011-01-13 16:14 ` Avi Kivity
2011-01-13 16:39 ` Anthony Liguori
2011-01-13 17:09 ` Paolo Bonzini
2011-01-13 20:38 ` Anthony Liguori
2011-01-13 17:13 ` Alexander Graf
2011-01-13 20:43 ` Anthony Liguori
2011-01-14 11:27 ` Gerd Hoffmann
2011-01-14 14:36 ` Alexander Graf
2011-01-14 14:56 ` [Spice-devel] " Frédéric Grelot
2011-01-14 15:13 ` Gerd Hoffmann
2011-01-14 15:28 ` Alexander Graf
2011-01-14 15:44 ` Alexander Graf
2011-01-14 16:31 ` Gerd Hoffmann
2011-01-14 16:42 ` Alexander Graf
2011-01-17 7:48 ` Gerd Hoffmann
2011-01-18 19:57 ` Alexander Graf
2011-01-15 12:07 ` Alon Levy
2011-01-14 15:37 ` Anthony Liguori
2011-01-14 16:26 ` Gerd Hoffmann
2011-01-14 17:02 ` Peter Maydell
2011-01-17 8:14 ` Gerd Hoffmann
2011-01-13 16:18 ` Avi Kivity
2011-01-13 16:43 ` Anthony Liguori
2011-01-13 17:19 ` Gerd Hoffmann
2011-01-13 19:21 ` Avi Kivity
2011-01-13 19:55 ` [Qemu-devel] Re: [Spice-devel] " Alon Levy
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=4D2EE756.2020808@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.