[Xen-changelog] [xen-unstable] No cpu_add_remove_lock in do_boot_cpu.

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

# HG changeset patch
# User Keir Fraser <keir.fraser@xxxxxxxxxx>
# Date 1269253782 0
# Node ID ab5f65e8137cb78afb96036522da5a7d1e00e52b
# Parent  4d3834df04831658eee8f2b7398443e24d4eb2fe
No cpu_add_remove_lock in do_boot_cpu.

The do_boot_cpu() will be called when system booting or CPU
online. When system booting, we don't need hold this lock. When system
online, the lock is held already by cpu_up.

Signed-off-by: Jiang, Yunhong <yunhong.jiang@xxxxxxxxx>
---
 xen/arch/x86/smpboot.c |    2 --
 1 files changed, 2 deletions(-)

diff -r 4d3834df0483 -r ab5f65e8137c xen/arch/x86/smpboot.c
--- a/xen/arch/x86/smpboot.c    Mon Mar 22 10:29:13 2010 +0000
+++ b/xen/arch/x86/smpboot.c    Mon Mar 22 10:29:42 2010 +0000
@@ -985,10 +985,8 @@ static int __devinit do_boot_cpu(int api
                cpucount--;
 
                /* Mark the CPU as non-present */
-               spin_lock(&cpu_add_remove_lock);
                x86_cpu_to_apicid[cpu] = BAD_APICID;
                cpu_clear(cpu, cpu_present_map);
-               spin_unlock(&cpu_add_remove_lock);
        } else {
        }
 

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog