On Fri, Aug 01, 2014 at 05:09:26PM +0200, Oleg Nesterov wrote:
> On 07/31, Paul E. McKenney wrote:
> >
> > +void synchronize_rcu_tasks(void)
> > +{
> > + /* Complain if the scheduler has not started. */
> > + rcu_lockdep_assert(!rcu_scheduler_active,
> > + "synchronize_rcu_tasks called too soon");
> > +
> > + /* Wait for the grace period. */
> > + wait_rcu_gp(call_rcu_tasks);
> > +}
>
> Btw, what about CONFIG_PREEMPT=n ?
>
> I mean, can't synchronize_rcu_tasks() be synchronize_sched() in this
> case?
Excellent point, indeed it can!
And if I do it right, it will make CONFIG_TASKS_RCU=y safe for kernel
tinification. ;-)
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/
