This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] No cpu_add_remove_lock in do_boot_cpu.
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 22 Mar 2010 03:35:14 -0700
Delivery-date: Mon, 22 Mar 2010 03:35:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@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
                /* 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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] No cpu_add_remove_lock in do_boot_cpu., Xen patchbot-unstable <=