Re: [tip:sched/core] sched/core: Add debugging code to catch missing update_rq_clock() calls

From
Peter Zijlstra <peterz@infradead.org>
Date
2017-02-03 08:53:56
Also in
linux-next, lkml
Reply to
Sachin Sant, 2017-02-03
On Fri, Feb 03, 2017 at 10:03:14AM +0530, Sachin Sant wrote:
quoted
On 02-Feb-2017, at 9:25 PM, Peter Zijlstra [off-list ref] wrote:

On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
quoted
On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith [off-list ref] wrote:
quoted
On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:

Could some of you test this? It seems to cure things in my (very)
limited testing.
I ran few cycles of cpu hot(un)plug tests. In most cases it works except one
where I ran into rcu stall:

[  173.493453] INFO: rcu_sched detected stalls on CPUs/tasks:
[  173.493473] 	8-...: (2 GPs behind) idle=006/140000000000000/0 softirq=0/0 fqs=2996 
[  173.493476] 	(detected by 0, t=6002 jiffies, g=885, c=884, q=6350)
Right, I actually saw that too, but I don't think that would be related
to my patch. I'll see if I can dig into this though, ought to get fixed
regardless.

Thanks for testing!
Thread (22 messages) 22 messages, 9 authors, last reply 2017-02-22
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help