xen: arm: enable aborts on all physical processors.

I'm not sure how this ended up in construct dom0 where it only affects the
boot cpu and doesn't logically fit.

Enable aborts at the same time as we enable interrupts.

I'm not sure what the behaviour of an "abort worthy" operation while aborts
are disable is, but it must surely be worse than calling do_unexpected_trap,
which is what happens from now on.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Acked-by: Tim Deegan <tim@xen.org>

diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index 0423b5a654e8d2b17e09b5ea83067a55871020a3..155b4363b51620db4f74dc088843e3a53de10df0 100644 (file)
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -633,8 +633,6 @@ int construct_dom0(struct domain *d)
         }
     }
 
-    local_abort_enable();
-
     return 0;
 }
 

diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index c22972f0deaeaecb4045f2de97052641fd63dfcd..2f9fdc805e700e7c3eb472fb24ffdcbb0333d3be 100644 (file)
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -488,6 +488,7 @@ void __init start_xen(unsigned long boot_phys_offset,
     arch_init_memory();
 
     local_irq_enable();
+    local_abort_enable();
 
     smp_prepare_cpus(cpus);
 

diff --git a/xen/arch/arm/smpboot.c b/xen/arch/arm/smpboot.c
index c7421fc793d7f5b2d373bb912d71311333d36b31..58951782135983c3cc3c82be1f2cc01e9e230d8a 100644 (file)
--- a/xen/arch/arm/smpboot.c
+++ b/xen/arch/arm/smpboot.c
@@ -175,6 +175,7 @@ void __cpuinit start_secondary(unsigned long boot_phys_offset,
     wmb();
 
     local_irq_enable();
+    local_abort_enable();
 
     printk(XENLOG_DEBUG "CPU %u booted.\n", smp_processor_id());