On Tue, 29 Sep 2015, Peter Zijlstra wrote:

> There is only a single PREEMPT_ACTIVE use in the regular __schedule()
> path and that is to circumvent the task->state check. Since the code
> setting PREEMPT_ACTIVE is the immediate caller of __schedule() we can
> replace this with a function argument.

Reviewed-by: Thomas Gleixner <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to