# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 9624fbe4b206ff39f422962b65adeeae90ff519d
# Parent ec7a1ffd0ade064c8ed79ec3fb2df9d5907866c1
[POWERPC][XEN] make sure Dom0.VCPU0 is pinned to the booting CPU
Signed-off-by: Jimi Xenidis <[EMAIL PROTECTED]>
---
xen/arch/powerpc/setup.c | 4 ++++
1 files changed, 4 insertions(+)
diff -r ec7a1ffd0ade -r 9624fbe4b206 xen/arch/powerpc/setup.c
--- a/xen/arch/powerpc/setup.c Fri Sep 01 12:31:56 2006 -0400
+++ b/xen/arch/powerpc/setup.c Fri Sep 01 12:37:29 2006 -0400
@@ -343,6 +343,10 @@ static void __init __start_xen(multiboot
if (NULL == alloc_vcpu(dom0, 0, 0))
panic("Error creating domain 0 vcpu 0\n");
+ /* The Interrupt Controller will route everything to CPU 0 so we
+ * need to make sure Dom0's vVCPU 0 is pinned to the CPU */
+ dom0->vcpu[0]->cpu_affinity = cpumask_of_cpu(0);
+
set_bit(_DOMF_privileged, &dom0->domain_flags);
/* post-create hooks sets security label */
acm_post_domain0_create(dom0->domain_id);
_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel
