WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] determining if a backend device is not working

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] determining if a backend device is not working
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Tue, 10 Mar 2009 12:46:36 +1100
Delivery-date: Mon, 09 Mar 2009 18:47:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmhIgybbc5MxlDyS1KuqiEOxhybGA==
Thread-topic: determining if a backend device is not working
In my gplpv drivers, the best I have come up with to determine if the
backend is not working is to wait for a few seconds (30 currently), and
if the backend state hasn't changed by then then I assume that it's
broken.

Is there a better way? The situation where this comes up is when
something like ',hdc:cdrom,r' is specified in the config file.

Even though I set all of the frontend up, the backend just stays at
state 2 instead of transitioning to 4.

Thanks

James

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