Peter Zijlstra fbd705a0c6 sched: Introduce the 'trace_sched_waking' tracepoint ... Mathieu reported that since 317f394160 ("sched: Move the second half of ttwu() to the remote cpu") trace_sched_wakeup() can happen out of context of the waker. This is a problem when you want to analyse wakeup paths because it is now very hard to correlate the wakeup event to whoever issued the wakeup. OTOH trace_sched_wakeup() is issued at the point where we set p->state = TASK_RUNNING, which is right were we hand the task off to the scheduler, so this is an important point when looking at scheduling behaviour, up to here its been the wakeup path everything hereafter is due to scheduler policy. To bridge this gap, introduce a second tracepoint: trace_sched_waking. It is guaranteed to be called in the waker context. Reported-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Francis Giraldeau <francis.giraldeau@gmail.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mike Galbraith <efault@gmx.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/20150609091336.GQ3644@twins.programming.kicks-ass.net Signed-off-by: Ingo Molnar <mingo@kernel.org>		2015-08-03 12:21:22 +02:00
..
events	sched: Introduce the 'trace_sched_waking' tracepoint	2015-08-03 12:21:22 +02:00
define_trace.h	tracing: Move the perf code out of trace_event.h	2015-05-13 14:05:10 -04:00
perf.h	tracing: Rename ftrace_get_offsets_##call() to trace_event_get_offsets_##call()	2015-05-13 21:49:01 -04:00
syscall.h	tracing: Rename ftrace_event_{call,class} to trace_event_{call,class}	2015-05-13 14:06:10 -04:00
trace_events.h	tracing: Rename ftrace_get_offsets_##call() to trace_event_get_offsets_##call()	2015-05-13 21:49:01 -04:00