[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1377821542.10300.869.camel@misato.fc.hp.com>
Date: Thu, 29 Aug 2013 18:12:22 -0600
From: Toshi Kani <toshi.kani@...com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: mingo@...hat.com, hpa@...ux.intel.com, tglx@...utronix.de,
gregkh@...uxfoundation.org, benh@...nel.crashing.org,
x86@...nel.org, linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org, fenghua.yu@...el.com, bp@...e.de,
srivatsa.bhat@...ux.vnet.ibm.com, isimatu.yasuaki@...fujitsu.com
Subject: Re: [PATCH 0/4] Unify CPU hotplug lock interface
On Fri, 2013-08-30 at 02:06 +0200, Rafael J. Wysocki wrote:
> On Thursday, August 29, 2013 11:15:10 AM Toshi Kani wrote:
> > On Sun, 2013-08-18 at 03:02 +0200, Rafael J. Wysocki wrote:
> > > On Saturday, August 17, 2013 01:46:55 PM 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().
> > > >
> > > > The patchset is based on Linus's tree, 3.11.0-rc5.
> > >
> > > Nice series, thanks a lot for taking care of this!
> >
> > Hi Rafael,
> >
> > Per the recent your changes in lock_device_hotplug(), do you think it
> > makes sense to integrate this patchset into your tree? I am also
> > considering to add one more patch to use lock_device_hotplug_sysfs() in
> > cpu_probe_store(). I will rebase to your tree and send them today if it
> > makes sense to you.
>
> Yes, it does to me.
Great! I will send them shortly.
Thanks,
-Toshi
--
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