xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joshua West <jwest@brandeis.edu>
To: xen-devel@lists.xensource.com
Subject: Re: pvfb: Absolute vs relative mouse tracking mystery
Date: Sun, 01 Aug 2010 15:11:09 -0400	[thread overview]
Message-ID: <4C55C6CD.40200@brandeis.edu> (raw)
In-Reply-To: <4C1F7E58.8030605@goop.org>

  On 06/21/2010 10:59 AM, Jeremy Fitzhardinge wrote:
> On 06/21/2010 03:57 PM, John Haxby wrote:
>> On 19/06/10 16:48, Jeremy Fitzhardinge wrote:
>>> 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.
>>>
>>>
>> Do you know what the changeset it?  This has been bugging me for a
>> while -- every now and again (just to taunt me) I get an absolute
>> pointer.
> It's in the qemu code, so you may need to explicitly make sure that has
> been updated: "cd tools/ioemu-remote; git pull".
>
>      J
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
Jeremy,

Do you know if this will be fixed in the Xen 3.4.x series as well?  In 
the 3.4.x ioemu-remote qemu code and the 2.6.18.8 xen kernel?

I ask because this is an issue for me on RHEL5 domU's which are 
paravirtualized.  Using Xen 3.4.3 w/ Xen kernel 2.6.18.8 and I'm not yet 
ready to switch production clusters to 4.0.x.

Thanks.

-- 
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu

  parent reply	other threads:[~2010-08-01 19:11 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
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 [this message]
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=4C55C6CD.40200@brandeis.edu \
    --to=jwest@brandeis.edu \
    --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).