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/
Home Products Support Community News


AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with pvops

To: "Carsten Schiers" <carsten@xxxxxxxxxx>
Subject: AW: Re: [Xen-devel] Xen BUG in mm / Xen 4.0.1 with pvops Kernel?
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Fri, 10 Sep 2010 09:48:33 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 10 Sep 2010 01:49:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <H000006700083044.1284056830.uhura.space.zz@MHS>
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: <4C88CBAD02000078000152AD@xxxxxxxxxxxxxxxxxx> <H000006700083044.1284056830.uhura.space.zz@MHS>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 09.09.10 at 20:27, "Carsten Schiers" <carsten@xxxxxxxxxx> wrote:
> and provided the output, just in case it is what you needed. I will for 
> sure need some time to understand that.
> Is the hypothesis that a) the BIOS is wrong, and b) Xen is checking more 
> extreme than bare metal, so we need to
> make the Xen Code a bit more relaxed (error message instead of crash)?

I think the underlying problem was pointed out before: The page table
accessor functions can't currently propagate errors, and hence
ioremap() can't be forced to fail if Xen refused a mapping. And then, as
I wrote in an earlier reply, the check for not trying to map RAM from
ioremap() is pretty pointless (and hence no help) currently for the Xen


Xen-devel mailing list

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