Xen 3.4.x and request-abs-pointer

[John Haxby <john.haxby@oracle.com>]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

A little while ago Jeremy Fitzhardinge was having some problem with 
absolute pointers.  This turned out to be a very simple fix in qemu-xen: 
wait for the frontend to be connected before connecting the backend.  
I've attached that original patch, if there's going to be a xen-3.4.4 it 
would be nice if this was included.

jch

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1037 bytes --]

commit 805ed3b20492d2f4bb465bfda65cedd286e23209
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date:   Fri May 21 15:46:55 2010 +0100

    Wait for frontend state Connected before connecting the backend
    
    The frontend of the framebuffer set a value (request-abs-pointer) and go
    to the state Connected.  The backend must read this value only when the
    frontend has the state Connected.
    
    From: Anthony PERARD <anthony.perard@citrix.com>
    Tested-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>

diff --git a/hw/xen_backend.c b/hw/xen_backend.c
index 76d07ec..31ed7b0 100644
--- a/hw/xen_backend.c
+++ b/hw/xen_backend.c
@@ -411,8 +411,7 @@ static int xen_be_try_connect(struct XenDevice *xendev)
 {
     int rc = 0;
 
-    if (xendev->fe_state != XenbusStateInitialised  &&
-	xendev->fe_state != XenbusStateConnected) {
+    if (xendev->fe_state != XenbusStateConnected) {
 	if (xendev->ops->flags & DEVOPS_FLAG_IGNORE_STATE) {
 	    xen_be_printf(xendev, 2, "frontend not ready, ignoring\n");
 	} else {

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel