From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: tglx@linutronix.de, peterz@infradead.org, tj@kernel.org,
oleg@redhat.com, paulmck@linux.vnet.ibm.com,
rusty@rustcorp.com.au, mingo@kernel.org,
akpm@linux-foundation.org, namhyung@kernel.org,
walken@google.com, vincent.guittot@linaro.org,
laijs@cn.fujitsu.com, rostedt@goodmis.org,
wangyun@linux.vnet.ibm.com, xiaoguangrong@linux.vnet.ibm.com,
sbw@mit.edu, fweisbec@gmail.com, zhong@linux.vnet.ibm.com,
nikunj@linux.vnet.ibm.com, linux-pm@vger.kernel.org,
linux-arch@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>,
Yong Zhang <yong.zhang0@gmail.com>,
Sanjay Lal <sanjayl@kymasys.com>,
"Steven J. Hill" <sjhill@mips.com>,
John Crispin <blogic@openwrt.org>,
Florian Fainelli <florian@openwrt.org>,
linux-mips@linux-mips.org
Subject: Re: [PATCH v2 38/45] MIPS: Use get/put_online_cpus_atomic() to prevent CPU offline
Date: Thu, 27 Jun 2013 12:38:31 +0530 [thread overview]
Message-ID: <51CBE4EF.5040302@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130626133912.GA4559@linux-mips.org>
On 06/26/2013 07:09 PM, Ralf Baechle wrote:
> On Wed, Jun 26, 2013 at 02:02:57AM +0530, Srivatsa S. Bhat wrote:
>
>> Once stop_machine() is gone from the CPU offline path, we won't be able
>> to depend on disabling preemption to prevent CPUs from going offline
>> from under us.
>>
>> Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going
>> offline, while invoking from atomic context.
>
> I think the same change also needs to be applied to r4k_on_each_cpu() in
> arch/mips/mm/c-r4k.c which currently looks like:
>
> static inline void r4k_on_each_cpu(void (*func) (void *info), void *info)
> {
> preempt_disable();
>
> #if !defined(CONFIG_MIPS_MT_SMP) && !defined(CONFIG_MIPS_MT_SMTC)
> smp_call_function(func, info, 1);
> #endif
> func(info);
> preempt_enable();
> }
>
Thanks for pointing this out! I'll include changes to this code in my
next version.
Regards,
Srivatsa S. Bhat
> This is a slightly specialized version of on_each_cpu() which only calls
> out to other CPUs in actual multi-core environments and also - unlike
> on_each_cpu() doesn't disable interrupts for the sake of better
> interrupt latencies.
>
> Which reminds me ...
>
> Andrew, I was wondering why did 78eef01b0fae087c5fadbd85dd4fe2918c3a015f
> [[PATCH] on_each_cpu(): disable local interrupts] disable interrupts?
> The log is:
>
> ----- snip -----
> When on_each_cpu() runs the callback on other CPUs, it runs with local
> interrupts disabled. So we should run the function with local interrupts
> disabled on this CPU, too.
>
> And do the same for UP, so the callback is run in the same environment on bo
> UP and SMP. (strictly it should do preempt_disable() too, but I think
> local_irq_disable is sufficiently equivalent).
> [...]
> ----- snip -----
>
> I'm not entirely convinced the symmetry between UP and SMP environments is
> really worth it. Would anybody mind removing the local_irq_disable() ...
> local_irq_enable() from on_each_cpu()?
>
prev parent reply other threads:[~2013-06-27 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130625202452.16593.22810.stgit@srivatsabhat.in.ibm.com>
2013-06-25 20:32 ` [PATCH v2 38/45] MIPS: Use get/put_online_cpus_atomic() to prevent CPU offline Srivatsa S. Bhat
2013-06-25 20:32 ` Srivatsa S. Bhat
2013-06-26 13:39 ` Ralf Baechle
2013-06-27 7:08 ` Srivatsa S. Bhat [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=51CBE4EF.5040302@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=blogic@openwrt.org \
--cc=david.daney@cavium.com \
--cc=florian@openwrt.org \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=sanjayl@kymasys.com \
--cc=sbw@mit.edu \
--cc=sjhill@mips.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=walken@google.com \
--cc=wangyun@linux.vnet.ibm.com \
--cc=xiaoguangrong@linux.vnet.ibm.com \
--cc=yong.zhang0@gmail.com \
--cc=zhong@linux.vnet.ibm.com \
/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