Hi Keir,
With the recent per cpu changes, scheduler_init() now starts poking
at per cpu space before we''ve configured it on ia64. This re-orders
the
setup calls to avoid this problem. Please apply. Thanks,
Alex
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
---
diff -r 1f05ac8abda6 xen/arch/ia64/xen/xensetup.c
--- a/xen/arch/ia64/xen/xensetup.c Tue Aug 08 09:26:10 2006 -0600
+++ b/xen/arch/ia64/xen/xensetup.c Tue Aug 08 12:18:04 2006 -0600
@@ -423,13 +423,14 @@ void start_kernel(void)
(xenheap_phys_end-__pa(heap_start)) >> 20,
(xenheap_phys_end-__pa(heap_start)) >> 10);
+ late_setup_arch(&cmdline);
+
scheduler_init();
idle_vcpu[0] = (struct vcpu*) ia64_r13;
idle_domain = domain_create(IDLE_DOMAIN_ID);
if ( (idle_domain == NULL) || (alloc_vcpu(idle_domain, 0, 0) =NULL) )
BUG();
- late_setup_arch(&cmdline);
alloc_dom_xen_and_dom_io();
setup_per_cpu_areas();
mem_init();
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel