From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvfb: Absolute vs relative mouse tracking mystery Date: Sat, 19 Jun 2010 16:48:46 +0100 Message-ID: <4C1CE6DE.8000602@goop.org> References: <4BE49501.6000408@goop.org> <4BE86945.9050408@goop.org> <20100619154145.GM17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100619154145.GM17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Xen-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 06/19/2010 04:41 PM, Pasi K=E4rkk=E4inen wrote: > On Tue, May 11, 2010 at 11:56:38AM +0100, Stefano Stabellini wrote: > =20 >> On Mon, 10 May 2010, Jeremy Fitzhardinge wrote: >> =20 >>> On 05/10/2010 07:41 AM, Stefano Stabellini wrote: >>> =20 >>>> On Fri, 7 May 2010, Jeremy Fitzhardinge wrote: >>>> =20 >>>> =20 >>>>> On one of my host machines, in PV guests using pvfb I get proper >>>>> absolute mouse tracking. >>>>> >>>>> On another host machine, I get relative tracking in pvfb-using gues= ts. >>>>> >>>>> Both are using identical versions of Fedora 12, identical domain >>>>> configs, and toolstacks and kernels built from the same source. Th= e log >>>>> files of the X servers are more or less identical. >>>>> >>>>> Help? Any clues? >>>>> >>>>> =20 >>>>> =20 >>>> relative vs absolute depends on a node on xenstore called >>>> "request-abs-pointer" that defaults to 0 and has to be written by th= e >>>> guest. >>>> =20 >>>> =20 >>> OK, it looks like it is being set, but the guest is still showing >>> relative behaviour: >>> >>> vkbd =3D "" >>> 0 =3D "" >>> backend =3D "/local/domain/0/backend/vkbd/5/0" >>> backend-id =3D "0" >>> state =3D "4" >>> page-ref =3D "1137660" >>> event-channel =3D "11" >>> request-abs-pointer =3D "1" >>> >>> Does this mean qemu-dm's vnc server is not doing the right thing? >>> =20 >> =20 >> I think is probably xenfb (that is the framebuffer backend in qemu) th= at >> is not doing the right thing. >> Try adding some debug output in hw/xenfb.c:input_connect. >> >> =20 > Jeremy: Did you figure this out? I'm again seeing this problem on my Fe= dora 13 + Xen 4.0.1-rc3-pre box.. > =20 Yes, that should be fixed in current xen-unstable - it was a xenbus race-condition. What guest are you seeing it in? I've found that I still don't get absolute pointers in Centos guests. J