ia64/xen-unstable

changeset 6390:603f55eaa690

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@xensource.com>
author kaf24@firebug.cl.cam.ac.uk
date Wed Aug 24 10:48:24 2005 +0000 (2005-08-24)
parents 342a53ce078b
children e75933e27215
files Config.mk linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c
line diff
     2.1 --- a/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c	Wed Aug 24 09:44:03 2005 +0000
     2.2 +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c	Wed Aug 24 10:48:24 2005 +0000
     2.3 @@ -128,8 +128,12 @@ static int __init init_syscall32(void)
     2.4  #endif
     2.5  	return 0;
     2.6  } 
     2.7 -	
     2.8 -__initcall(init_syscall32); 
     2.9 +
    2.10 +/*
    2.11 + * This must be done early in case we have an initrd containing 32-bit
    2.12 + * binaries (e.g., hotplug). This could be pushed upstream to arch/x86_64.
    2.13 + */	
    2.14 +core_initcall(init_syscall32); 
    2.15  
    2.16  /* May not be __init: called during resume */
    2.17  void syscall32_cpu_init(void)