On Wed, Aug 13, 2014 at 06:35:22PM +0200, Peter Zijlstra wrote:
> On Wed, Aug 13, 2014 at 07:43:32AM -0700, Paul E. McKenney wrote:
> > So the first three look OK to hook rcu_idle_enter() and rcu_idle_exit()
> > into, but the last two don't look so good.
> >
> > That said, if you are OK not tracing the stuff under
> > stop_critical_timings(),
> > then I can use the RCU dyntick-idle state and not wake anything up.
>
> Either way, Steve could easily whip up a debug thing that could validate
> that. Simply WARN whenever an __mcount happens when under rcu_idle.
>
> And if we make these idle functions small enough that should not be a
> problem at all.
Right now, the CPU-idle drivers look quite hairy and error-prone.
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
