From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=57296 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PdLig-0001B9-UO
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 06:51:59 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PdLif-00065X-OT
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 06:51:58 -0500
Received: from mx1.redhat.com ([209.132.183.28]:38793)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PdLif-00065S-DI
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 06:51:57 -0500
Message-ID: <4D2EE756.2020808@redhat.com>
Date: Thu, 13 Jan 2011 12:51:50 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
References: <4D2ED1C8.7070304@redhat.com>
	<AANLkTikECZUmQKQpmRPQv5QcOs=oKJG_E0ySQBxnWpU3@mail.gmail.com>
In-Reply-To: <AANLkTikECZUmQKQpmRPQv5QcOs=oKJG_E0ySQBxnWpU3@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: [Spice-devel] paravirtual mouse/tablet
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: spice-devel <spice-devel@lists.freedesktop.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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