Searched hist:"4 ee7c60de83ac01fa4c33c55937357601631e8ad" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/trace/events/ |
| H A D | initcall.h | 4ee7c60de83ac01fa4c33c55937357601631e8ad Fri Mar 23 09:18:03 CDT 2018 Steven Rostedt (VMware) <rostedt@goodmis.org> 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>
|
| /openbmc/linux/init/ |
| H A D | main.c | diff 4ee7c60de83ac01fa4c33c55937357601631e8ad Fri Mar 23 09:18:03 CDT 2018 Steven Rostedt (VMware) <rostedt@goodmis.org> 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>
|