* Peter Zijlstra pet...@infradead.org wrote:
On Thu, Apr 02, 2015 at 12:42:27PM +0200, Ingo Molnar wrote:
So why not use a suitable CPU_DOWN* notifier for this, instead of open
coding it all into a random place in the hotplug machinery?
Because notifiers are crap? ;-) [...]
No doubt -
On Thu, Apr 02, 2015 at 02:12:47PM +0200, Ingo Molnar wrote:
Okay. I'll resurrect the fix with a hotplug_cpu__tick_pull() name -
agreed?
Sure.
Also, I improved the changelog (attached below), but decided
against applying it until these questions are cleared - please use
that for
On 04/02/2015 04:12 PM, Ingo Molnar wrote:
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or rcu_sched stall warnings. The issue was
traced to commit 7cba160ad789a powernv/cpuidle: Redesign
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
On 04/02/2015 04:12 PM, Ingo Molnar wrote:
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or rcu_sched stall warnings. The issue
On Thu, Apr 02, 2015 at 12:42:27PM +0200, Ingo Molnar wrote:
So why not use a suitable CPU_DOWN* notifier for this, instead of open
coding it all into a random place in the hotplug machinery?
Because notifiers are crap? ;-) Its entirely impossible to figure out
what's happening to core code in
On 04/02/2015 05:01 PM, Ingo Molnar wrote:
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
On 04/02/2015 04:12 PM, Ingo Molnar wrote:
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or
On 04/02/2015 05:42 PM, Ingo Molnar wrote:
* Peter Zijlstra pet...@infradead.org wrote:
On Thu, Apr 02, 2015 at 12:42:27PM +0200, Ingo Molnar wrote:
So why not use a suitable CPU_DOWN* notifier for this, instead of open
coding it all into a random place in the hotplug machinery?
Because
* Preeti U Murthy pre...@linux.vnet.ibm.com wrote:
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or rcu_sched stall warnings. The issue was
traced to commit 7cba160ad789a powernv/cpuidle: Redesign idle states
management, which exposed the
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or rcu_sched stall warnings. The issue was
traced to commit 7cba160ad789a powernv/cpuidle: Redesign idle states
management, which exposed the cpu down race with hrtimer based broadcast
mode(Commit
On Mon, 30 Mar 2015, Preeti U Murthy wrote:
It was found when doing a hotplug stress test on POWER, that the machine
either hit softlockups or rcu_sched stall warnings. The issue was
traced to commit 7cba160ad789a powernv/cpuidle: Redesign idle states
management, which exposed the cpu down
10 matches
Mail list logo