[Xen-changelog] [xen-unstable] [POWERPC][XEN] make sure Dom0.VCPU0 is pinned to the booting CPU

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

# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID 18b3cbb04dc36d9bd6b760cc47901bce3a77fd48
# Parent  0e02ac68b01bdda0b24c75985a81f6416b6488c5
[POWERPC][XEN] make sure Dom0.VCPU0 is pinned to the booting CPU

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Signed-off-by: Hollis Blanchard <hollisb@xxxxxxxxxx>
---
 xen/arch/powerpc/setup.c |    4 ++++
 1 files changed, 4 insertions(+)

diff -r 0e02ac68b01b -r 18b3cbb04dc3 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
@@ -344,6 +344,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-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog