Files
linux/include/trace/events
Steven Rostedt (VMware) 4ee7c60de8 init, tracing: Add initcall trace events
Being able to trace the start and stop of initcalls is useful to see where
the timings are an issue. There is already an "initcall_debug" parameter,
but that can cause a large overhead itself, as the printing of the
information may take longer than the initcall functions.

Adding in a start and finish trace event around the initcall functions, as
well as a trace event that records the level of the initcalls, one can get a
much finer measurement of the times and interactions of the initcalls
themselves, as trace events are much lighter than printk()s.

Suggested-by: Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
2018-04-06 08:56:54 -04:00
..
2017-12-13 15:10:01 -05:00
2018-01-22 16:08:14 +01:00
2017-09-25 20:38:26 +02:00
2017-11-15 18:21:06 -08:00
2017-11-24 10:18:42 +00:00
2017-12-19 10:56:24 +01:00
2018-01-02 14:27:30 -05:00