On Mon, Sep 09, 2013 at 09:41:32AM -0400, Steven Rostedt wrote:
> On Mon, 9 Sep 2013 15:29:02 +0200
> Frederic Weisbecker <fweis...@gmail.com> wrote:
>
>
> > No, putting that on the task_struct won't help much in this regard I think.
> > Regular schedule() calls don't change that per cpu state.
>
> But is there a place that it would need to?
>
> I mean, if RCU is not tracking a CPU, is it safe to call schedule().
> And then how would the new task know that RCU is ignoring that CPU?
Guys, RCU really is tracking per-CPU state with the rcu_dynticks.dynticks
field.
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/
