From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
spice-devel <spice-devel@lists.freedesktop.org>
Subject: Re: [Qemu-devel] Re: [Spice-devel] paravirtual mouse/tablet
Date: Thu, 13 Jan 2011 14:41:22 -0600 [thread overview]
Message-ID: <4D2F6372.1010707@codemonkey.ws> (raw)
In-Reply-To: <4D2F31A7.1060402@redhat.com>
On 01/13/2011 11:08 AM, Gerd Hoffmann wrote:
> On 01/13/11 16:55, Anthony Liguori wrote:
>> On 01/13/2011 05:51 AM, Gerd Hoffmann wrote:
>>> 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).
>>>
>>
>> Would be slightly cleaner to have multiple devices.
>
> Yea, right, that would work too. If we have some way to assign a
> display to a pvmouse device this works equally well.
I think that has to be outside of the device. There are so many ways to
map mice to multi heads. In fact, one mouse could easily map to a
single device. It's almost something that really should be part of the
guest configuration.
>> That maybe implies that we need an offscreen coordinate for the
>> mouse so that you can hide the mouse when it leaves one window.
>
> Hmm? I fail to see why multihead is special here.
If you show two mice in the guest, would X render two cursors?
Regards,
Anthony Liguori
> cheers,
> Gerd
>
next prev parent reply other threads:[~2011-01-13 20:41 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
2011-01-13 15:55 ` Anthony Liguori
2011-01-13 17:08 ` Gerd Hoffmann
2011-01-13 20:41 ` Anthony Liguori [this message]
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=4D2F6372.1010707@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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 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).