Valentin Schneider fa2c3254d7 sched/tracing: Don't re-read p->state when emitting sched_switch event ... As of commit c6e7bd7afa ("sched/core: Optimize ttwu() spinning on p->on_cpu") the following sequence becomes possible: p->__state = TASK_INTERRUPTIBLE; __schedule() deactivate_task(p); ttwu() READ !p->on_rq p->__state=TASK_WAKING trace_sched_switch() __trace_sched_switch_state() task_state_index() return 0; TASK_WAKING isn't in TASK_REPORT, so the task appears as TASK_RUNNING in the trace event. Prevent this by pushing the value read from __schedule() down the trace event. Reported-by: Abhijeet Dharmapurikar <adharmap@quicinc.com> Signed-off-by: Valentin Schneider <valentin.schneider@arm.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org> Link: https://lore.kernel.org/r/20220120162520.570782-2-valentin.schneider@arm.com		2022-03-01 16:18:39 +01:00
..
events	sched/tracing: Don't re-read p->state when emitting sched_switch event	2022-03-01 16:18:39 +01:00
bpf_probe.h	tracing: Add '__rel_loc' using trace event macros	2021-12-06 15:37:21 -05:00
define_trace.h	tracepoint: Optimize using static_call()	2020-09-01 09:58:06 +02:00
perf.h	tracing/perf: Avoid -Warray-bounds warning for __rel_loc macro	2022-01-27 19:15:45 -05:00
syscall.h	tracepoints: Migrate to use SYSCALL_WORK flag	2020-11-16 21:53:15 +01:00
trace_events.h	tracing/perf: Avoid -Warray-bounds warning for __rel_loc macro	2022-01-27 19:15:45 -05:00