-
由 Peter Zijlstra 提交于
For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't useful because we can get preempted with current->state != TASK_RUNNING without actually getting removed from the runqueue. Cure this by treating all preempted tasks as runnable from the tracer's point of view. Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl> Cautiously-acked-by: NSteven Rostedt <rostedt@goodmis.org> LKML-Reference: <1275322715.27810.23323.camel@twins> Signed-off-by: NIngo Molnar <mingo@elte.hu>
02f72694