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


[Xen-devel] Re: [bisected] 2.6.31 regression: fails to boot as xen guest

To: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [bisected] 2.6.31 regression: fails to boot as xen guest
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 25 Aug 2009 12:31:52 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Arnd Hannemann <hannemann@xxxxxxxxxxxxxxxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, "hannes@xxxxxxxxxxx" <hannes@xxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, Arnd Hannemann <Arnd.Hannemann@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 25 Aug 2009 12:32:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1251225834.13451.13.camel@penberg-laptop>
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: <4A9407B1.6020400@xxxxxxxxxxxxxxxxxxx> <84144f020908250929t7d4a74f1n4827de04e5c4c56a@xxxxxxxxxxxxxx> <4A94161A.2020609@xxxxxxxxxxxxxxxxxxx> <1251219129.4852.1.camel@penberg-laptop> <4A94242E.30309@xxxxxxxxxxxxxxxxxxx> <1251223399.13451.5.camel@penberg-laptop> <4A942BDD.70303@xxxxxxxxxxxxxxxxxxx> <20090825182510.GA6903@xxxxxxx> <4A942DB9.3020209@xxxxxxxx> <4A942F96.7000900@xxxxxxxxxxxxxxxxxxx> <1251225834.13451.13.camel@penberg-laptop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 08/25/09 11:43, Pekka Enberg wrote:
> Aha, the previous patch worked because I #ifdef the WP test completely.
> Jeremy, the root cause here is that we do the WP test much earlier than
> before. Even with the test moved to trap_init(), we do it early compared
> to what we did before.
> I guess Xen is not prepared to handle traps this early in the boot
> sequence? Can we fix that?

The crash is in the event (interrupt) path, which shouldn't be involved
in trap handling at all.  I'm wondering if interrupts are getting
enabled as a side-effect of handling the trap.


Xen-devel mailing list

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