From: Toshi Kani <toshi.kani@hp.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: mingo@redhat.com, hpa@linux.intel.com, tglx@linutronix.de,
gregkh@linuxfoundation.org, benh@kernel.crashing.org,
x86@kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, fenghua.yu@intel.com, bp@suse.de,
srivatsa.bhat@linux.vnet.ibm.com, isimatu.yasuaki@jp.fujitsu.com
Subject: Re: [PATCH 0/4] Unify CPU hotplug lock interface
Date: Thu, 29 Aug 2013 18:12:22 -0600 [thread overview]
Message-ID: <1377821542.10300.869.camel@misato.fc.hp.com> (raw)
In-Reply-To: <21553065.6VHCMzStpF@vostro.rjw.lan>
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
prev parent reply other threads:[~2013-08-30 0:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 19:46 Toshi Kani
2013-08-17 19:46 ` [PATCH 1/4] hotplug, x86: Fix online state in cpu0 debug interface Toshi Kani
2013-08-18 0:59 ` Rafael J. Wysocki
2013-08-17 19:46 ` [PATCH 2/4] hotplug, x86: Add hotplug lock to missing places Toshi Kani
2013-08-17 23:15 ` Greg KH
2013-08-19 14:53 ` Toshi Kani
2013-08-18 0:59 ` Rafael J. Wysocki
2013-08-17 19:46 ` [PATCH 3/4] hotplug, x86: Disable ARCH_CPU_PROBE_RELEASE on x86 Toshi Kani
2013-08-18 1:00 ` Rafael J. Wysocki
2013-08-17 19:46 ` [PATCH 4/4] hotplug, powerpc, x86: Remove cpu_hotplug_driver_lock() Toshi Kani
2013-08-18 1:01 ` Rafael J. Wysocki
2013-08-19 15:20 ` Nathan Fontenot
2013-08-19 15:23 ` Toshi Kani
2013-08-18 1:02 ` [PATCH 0/4] Unify CPU hotplug lock interface Rafael J. Wysocki
2013-08-19 14:54 ` Toshi Kani
2013-08-29 17:15 ` Toshi Kani
2013-08-30 0:06 ` Rafael J. Wysocki
2013-08-30 0:12 ` Toshi Kani [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1377821542.10300.869.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=benh@kernel.crashing.org \
--cc=bp@suse.de \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@linux.intel.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome