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

Re: [Xen-devel] Crash during boot in Debian lenny default dom0 kernel (

To: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Crash during boot in Debian lenny default dom0 kernel (2.6.26-2-xen-686)
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Thu, 25 Feb 2010 13:10:40 +0000
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, Yunhong Jiang <yunhong.jiang@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 25 Feb 2010 05:11:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <de76405a1002250346q32cf093i58429407ccfb5f32@xxxxxxxxxxxxxx>
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>
References: <de76405a1002241047w4d138abbjc872c371c0e742ed@xxxxxxxxxxxxxx> <25841307.20100224200810@xxxxxxxxxxxxxx> <20100224202009.GE2761@xxxxxxxxxxx> <de76405a1002241557y4449110v37b811fd36c60c4d@xxxxxxxxxxxxxx> <C8EDE645B81E5141A8C6B2F73FD92651247A93D81D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <de76405a1002250248wcc16101v644f409f73dd43b1@xxxxxxxxxxxxxx> <4B8665680200007800031406@xxxxxxxxxxxxxxxxxx> <de76405a1002250346q32cf093i58429407ccfb5f32@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> George Dunlap <George.Dunlap@xxxxxxxxxxxxx> 25.02.10 12:46 >>>
>Given that this is already in a major distribution, is there any way
>we can fail gracefully if someone's running this kernel?  I'm not
>familiar enough with the MSI to know if this is possible, or what a
>good set of "sanity checks" would be for failing the hypercall.

Checking for a suitably aligned and within PADDR_BITS range would
certainly be doable, but I question the sense. Such a check would
prevent the crash, but it wouldn't guarantee the system would work
(and may result in more subtle crashes).

Jan


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

<Prev in Thread] Current Thread [Next in Thread>