From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: John Haxby <john.haxby@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Patch 0/2] Fix request-abs-pointer (again)
Date: Wed, 7 Jul 2010 11:55:17 -0400 [thread overview]
Message-ID: <20100707155517.GA5773@phenom.dumpdata.com> (raw)
In-Reply-To: <1278510002-20735-1-git-send-email-john.haxby@oracle.com>
On Wed, Jul 07, 2010 at 02:40:00PM +0100, John Haxby wrote:
> A little while ago, Jeremy Fitzhardinge has a problem that was preventing
> request-abs-pointer from being honoured. A simple fix for this in
> 805ed3b20492d2f4bb465bfda65cedd286e23209 actually turned out to be wrong.
>
> Konrad Rzeszutek Wilk and Stefano Stabellini suggested a different
> approach: introduce a new hook in xen_backend that, if defined, is called
> when the frontend is connected. The first of these two patches does just
> that (the old connect hook is now called "initialise" and the new hook is
> called "connected"). The second patch uses this to set up the pointer at
> the right time. I haven't been able to test this in a Xen 4.0
> environment, but it works properly in a Xen 3.4 environment.
I tested them by:
1). Reverting c/s 21260 and 21651 from Xen unstable
2). Applied both of your patches on top of
add968aaf68cb57257428f8cfadb209f2614a6d8
and tested the pv-grub launch with success.
I did not test the HVM stubdomain launch.
prev parent reply other threads:[~2010-07-07 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 13:40 [Patch 0/2] Fix request-abs-pointer (again) John Haxby
2010-07-07 13:40 ` [PATCH 1/2] Introduce a new 'connected' xendev op called when Connected John Haxby
2010-07-07 16:40 ` Stefano Stabellini
2010-07-07 13:40 ` [PATCH 2/2] Move the xenfb pointer handler to the connected method John Haxby
2010-07-07 16:41 ` Stefano Stabellini
2010-07-07 15:55 ` Konrad Rzeszutek Wilk [this message]
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=20100707155517.GA5773@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=john.haxby@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.