From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=33699 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PdJRM-00053K-F7 for qemu-devel@nongnu.org; Thu, 13 Jan 2011 04:25:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PdJRL-0002ZF-Li for qemu-devel@nongnu.org; Thu, 13 Jan 2011 04:25:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48634) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PdJRL-0002Yk-El for qemu-devel@nongnu.org; Thu, 13 Jan 2011 04:25:55 -0500 Message-ID: <4D2EC517.8090703@redhat.com> Date: Thu, 13 Jan 2011 10:25:43 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Spice-devel] [Qemu-devel] spicevmv chardev, guest agents and paravirtual mouse References: <4D2DD2F1.6030801@redhat.com> <4D2DE7AA.3010202@codemonkey.ws> <4D2DFA1C.9010901@redhat.com> <4D2E0250.6090402@codemonkey.ws> In-Reply-To: <4D2E0250.6090402@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Hans de Goede , "qemu-devel@nongnu.org" , spice-devel Hi, >>>> The VDAgentMouseState messages have one problem: They send the pointer >>>> position as-is, which introduces a dependency on the screen size. >> >> Yeah, if we could get rid of that, that would be great. We could even >> introduce a new mouse message type to the existing spice vdagent protocol >> and use capabilities to switch between the 2. > > I think the typical trick is to scale the coordinates to some large > resolution. Would there be any issue doing this in vdagent today? No. The vdagent actually registers a uinput device with the size matching the screen resolution today. It could also register a tablet with a -- say -- 65536 x 65536 resolution and scale. Even better would be to let spice-server or qemu do the scaling and feed vdagent/pvmouse with already scaled coordinates, so the vdagent doesn't has to hop through the loops Hans described to get the screen resolution coordinates. qemu already uses a 0 -> 0xffff range internally for absolute input coordinates, the pvmouse (or should we better name it pvtablet?) should probably pass those values as-is to the guest. cheers, Gerd