[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <522006F6.2060206@jp.fujitsu.com>
Date: Fri, 30 Aug 2013 11:44:06 +0900
From: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
To: Toshi Kani <toshi.kani@...com>
CC: <rjw@...k.pl>, <mingo@...hat.com>, <hpa@...ux.intel.com>,
<tglx@...utronix.de>, <gregkh@...uxfoundation.org>,
<benh@...nel.crashing.org>, <linux-acpi@...r.kernel.org>,
<x86@...nel.org>, <linuxppc-dev@...ts.ozlabs.org>,
<linux-kernel@...r.kernel.org>, <nfont@...ux.vnet.ibm.com>,
<fenghua.yu@...el.com>, <bp@...e.de>,
<srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2 0/4] Unify CPU hotplug lock interface
(2013/08/30 9:22), Toshi Kani wrote:
> lock_device_hotplug() was recently introduced to serialize CPU & Memory
> online/offline and hotplug operations, along with sysfs online interface
> restructure (commit 4f3549d7). With this new locking scheme,
> cpu_hotplug_driver_lock() is redundant and is no longer necessary.
>
> This patchset makes sure that lock_device_hotplug() covers all CPU online/
> offline interfaces, and then removes cpu_hotplug_driver_lock().
>
> v2:
> - Rebased to the pm tree, bleeding-edge.
> - Changed patch 2/4 to use lock_device_hotplug_sysfs().
>
> ---
> Toshi Kani (4):
> hotplug, x86: Fix online state in cpu0 debug interface
> hotplug, x86: Add hotplug lock to missing places
> hotplug, x86: Disable ARCH_CPU_PROBE_RELEASE on x86
> hotplug, powerpc, x86: Remove cpu_hotplug_driver_lock()
>
> ---
The patch-set looks good to me.
Acked-by: Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>
Thanks,
Yasuaki Ishimatsu
> arch/powerpc/kernel/smp.c | 12 ----------
> arch/powerpc/platforms/pseries/dlpar.c | 40 +++++++++++++---------------------
> arch/x86/Kconfig | 4 ----
> arch/x86/kernel/smpboot.c | 21 ------------------
> arch/x86/kernel/topology.c | 11 ++++++----
> drivers/base/cpu.c | 34 +++++++++++++++++++----------
> include/linux/cpu.h | 13 -----------
> 7 files changed, 45 insertions(+), 90 deletions(-)
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists