[Xen-changelog] Initialise syscall32 vsyscall page early, as it may be needed

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID 603f55eaa690ef8d47e54bdb57e20fb3266d8f56
# Parent  342a53ce078b77fe6ec95dd33b011e9cb9a129d2
Initialise syscall32 vsyscall page early, as it may be needed
for some initcalls (e.g., if initrd /bin/hotplug is an i386
binary).

Signed-off-by: Keir Fraser <keir@xxxxxxxxxxxxx>

diff -r 342a53ce078b -r 603f55eaa690 
linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c
--- a/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c     Wed Aug 24 
09:44:03 2005
+++ b/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c     Wed Aug 24 
10:48:24 2005
@@ -128,8 +128,12 @@
 #endif
        return 0;
 } 
-       
-__initcall(init_syscall32); 
+
+/*
+ * This must be done early in case we have an initrd containing 32-bit
+ * binaries (e.g., hotplug). This could be pushed upstream to arch/x86_64.
+ */    
+core_initcall(init_syscall32); 
 
 /* May not be __init: called during resume */
 void syscall32_cpu_init(void)

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