xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: pvfb: Absolute vs relative mouse tracking mystery
Date: Thu, 22 Jul 2010 11:52:38 +0300	[thread overview]
Message-ID: <20100722085238.GP17817@reaktio.net> (raw)
In-Reply-To: <4C479868.1030806@goop.org>

On Wed, Jul 21, 2010 at 06:01:28PM -0700, Jeremy Fitzhardinge wrote:
> >>>>>>>>                 
> >>>>>>>>> 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 guests.
> >>>>>>>>>
> >>>>>>>>> Both are using identical versions of Fedora 12, identical domain
> >>>>>>>>> configs, and toolstacks and kernels built from the same source.  The log
> >>>>>>>>> files of the X servers are more or less identical.
> >>>>>>>>>
> >>>>>>>>> Help?  Any clues?
> >>>>>>>>>
> >>>>>>>>>     
> >>>>>>>>>           
> >>>>>>>>>               
> >>>>>>>>>                   
> >>>>>>>> relative vs absolute depends on a node on xenstore called
> >>>>>>>> "request-abs-pointer" that defaults to 0 and has to be written by the
> >>>>>>>> guest.
> >>>>>>>>   
> >>>>>>>>         
> >>>>>>>>             
> >>>>>>>>                 
> >>>>>>> OK, it looks like it is being set, but the guest is still showing
> >>>>>>> relative behaviour:
> >>>>>>>
> >>>>>>>     vkbd = ""
> >>>>>>>      0 = ""
> >>>>>>>       backend = "/local/domain/0/backend/vkbd/5/0"
> >>>>>>>       backend-id = "0"
> >>>>>>>       state = "4"
> >>>>>>>       page-ref = "1137660"
> >>>>>>>       event-channel = "11"
> >>>>>>>       request-abs-pointer = "1"
> >>>>>>>
> >>>>>>> Does this mean qemu-dm's vnc server is not doing the right thing?
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>>  
> >>>>>> I think is probably xenfb (that is the framebuffer backend in qemu) that
> >>>>>> is not doing the right thing.
> >>>>>> Try adding some debug output in hw/xenfb.c:input_connect.
> >>>>>>
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> Jeremy: Did you figure this out? I'm again seeing this problem on my Fedora 13 + Xen 4.0.1-rc3-pre box..
> >>>>>   
> >>>>>       
> >>>>>           
> >>>> 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.
> >>>>
> >>>>     
> >>>>         
> >>> Yeah, it's a CentOS 5.5 guest that gets relative pointer on my Fedora 13 dom0.
> >>> On a CentOS5 dom0 it gets absolute though..
> >>>
> >>> Fedora 13 guest gets absolute pointer on my Fedora 13 dom0..
> >>>   
> >>>       
> >> Huh, that is interesting.  Maybe there's still a race or something there...
> >>
> >>     
> > Yeah.. maybe. Note that I'm running Xen 4.0.1-rc3-pre and not xen-unstable..
> >   
> 
> I just got a Win7 hvm domain working for the first time in a while, and
> found that it *isn't* getting proper abs updates.  I even set
> usbdevice='tablet' in its config...
> 

Ok. And reading my own lines above, I realize F13 worked for me earlier,
but it was centos 5.5 that didn't work.

I'll have to re-test things here aswell :)

-- Pasi

  reply	other threads:[~2010-07-22  8:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 22:32 pvfb: Absolute vs relative mouse tracking mystery Jeremy Fitzhardinge
2010-05-10 14:41 ` Stefano Stabellini
2010-05-10 17:45   ` Jeremy Fitzhardinge
2010-05-10 20:15   ` Jeremy Fitzhardinge
2010-05-11 10:56     ` Stefano Stabellini
2010-06-19 15:41       ` Pasi Kärkkäinen
2010-06-19 15:48         ` Jeremy Fitzhardinge
2010-06-19 16:22           ` Pasi Kärkkäinen
2010-06-19 17:40             ` Jeremy Fitzhardinge
2010-06-19 17:50               ` Pasi Kärkkäinen
2010-07-22  1:01                 ` Jeremy Fitzhardinge
2010-07-22  8:52                   ` Pasi Kärkkäinen [this message]
2010-07-22 19:04                     ` John Haxby
2010-07-22 19:13                       ` Jeremy Fitzhardinge
2010-07-23 11:33                         ` John Haxby
2010-07-22 11:58                   ` Stefano Stabellini
2010-07-22 16:51                     ` Jeremy Fitzhardinge
2010-07-22 16:58                       ` Jeremy Fitzhardinge
2010-07-23 11:55                         ` Stefano Stabellini
2010-06-21 14:57           ` John Haxby
2010-06-21 14:59             ` Jeremy Fitzhardinge
2010-07-21 11:52               ` Pasi Kärkkäinen
2010-08-01 19:11               ` Joshua West
2010-08-02 19:00                 ` Jeremy Fitzhardinge
2010-08-02 19:37                   ` Joshua West
2010-08-02 19:40                     ` Jeremy Fitzhardinge
2010-08-03 16:23                       ` John Haxby
2010-08-04  0:35                         ` Joshua West
2010-08-10 16:20                           ` John Haxby

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=20100722085238.GP17817@reaktio.net \
    --to=pasik@iki.fi \
    --cc=anthony.perard@citrix.com \
    --cc=jeremy@goop.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).