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] [PATCH] get_current() called before set_current()

To: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] get_current() called before set_current()
From: "Charles Coffing" <ccoffing@xxxxxxxxxx>
Date: Tue, 31 Aug 2004 13:19:37 -0600
Delivery-date: Tue, 31 Aug 2004 20:30:01 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
The recent change that added debugging to spinlocks (cset 1.1278.1.1)
caused get_current() to be called earlier in the boot process.  In fact,
it is now called before set_current().

If assertions are compiled in, this ultimately causes a triple fault
when Xen tries to print the banner.  If assertions aren't compiled in,
memory corruption results (although currently this corruption appears to
be benign.)

The attached patch moves the first set_current() call a bit earlier in
the boot process.

Thanks,
Charles

Attachment: setcurrent.patch
Description: Binary data

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