summaryrefslogtreecommitdiff
path: root/net/lapb/lapb_iface.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2018-03-23 10:18:03 -0400
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2018-04-06 08:56:54 -0400
commit4ee7c60de83ac01fa4c33c55937357601631e8ad (patch)
tree782bae7199ba64345a70e7094f270dea434331ee /net/lapb/lapb_iface.c
parent8ec8405f081e1e0f800b20f683451c37e81e26c1 (diff)
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>
Diffstat (limited to 'net/lapb/lapb_iface.c')
0 files changed, 0 insertions, 0 deletions