ia64/xen-unstable

changeset 11497:18b3cbb04dc3

[POWERPC][XEN] make sure Dom0.VCPU0 is pinned to the booting CPU

Signed-off-by: Jimi Xenidis <jimix@watson.ibm.com>
Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
author Jimi Xenidis <jimix@watson.ibm.com>
date Fri Sep 01 12:37:29 2006 -0400 (2006-09-01)
parents 0e02ac68b01b
children 94aa7e921ccd
files xen/arch/powerpc/setup.c
line diff
     1.1 --- a/xen/arch/powerpc/setup.c	Fri Sep 01 12:31:56 2006 -0400
     1.2 +++ b/xen/arch/powerpc/setup.c	Fri Sep 01 12:37:29 2006 -0400
     1.3 @@ -344,6 +344,10 @@ static void __init __start_xen(multiboot
     1.4      if (NULL == alloc_vcpu(dom0, 0, 0))
     1.5          panic("Error creating domain 0 vcpu 0\n");
     1.6  
     1.7 +    /* The Interrupt Controller will route everything to CPU 0 so we
     1.8 +     * need to make sure Dom0's vVCPU 0 is pinned to the CPU */
     1.9 +    dom0->vcpu[0]->cpu_affinity = cpumask_of_cpu(0);
    1.10 +
    1.11      set_bit(_DOMF_privileged, &dom0->domain_flags);
    1.12      /* post-create hooks sets security label */
    1.13      acm_post_domain0_create(dom0->domain_id);