On Fri, 11 May 2018 12:25:28 -0400 Steven Rostedt <rost...@goodmis.org> wrote:
> I would also say that one should never call schedule() directly without > changing its state to something other than TASK_RUNNING. Hence, calling > schedule directly is saying you are ready to sleep. But that is not the > case with cond_resched() which should always be called with the state > as TASK_RUNNING. To continue this, with tracing, when a task is scheduled out in the RUNNING state, it is considered preempted, otherwise it is not. -- Steve