From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=50822 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PdQfu-0004G5-Vv
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 12:09:31 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PdQfh-000542-7u
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 12:09:14 -0500
Received: from mx1.redhat.com ([209.132.183.28]:7964)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kraxel@redhat.com>) id 1PdQfh-00053n-0p
	for qemu-devel@nongnu.org; Thu, 13 Jan 2011 12:09:13 -0500
Message-ID: <4D2F31A7.1060402@redhat.com>
Date: Thu, 13 Jan 2011 18:08:55 +0100
From: Gerd Hoffmann <kraxel@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [Spice-devel] paravirtual mouse/tablet
References: <4D2ED1C8.7070304@redhat.com>	<AANLkTikECZUmQKQpmRPQv5QcOs=oKJG_E0ySQBxnWpU3@mail.gmail.com>
	<4D2EE756.2020808@redhat.com> <4D2F2085.204@codemonkey.ws>
In-Reply-To: <4D2F2085.204@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, spice-devel <spice-devel@lists.freedesktop.org>

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.

> 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.

cheers,
   Gerd