[PATCH 1/4 v2] init, tracing: Add initcall trace events

From: "Steven Rostedt (VMware)" 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

[PATCH 1/4 v2] init, tracing: Add initcall trace events

From: "Steven Rostedt (VMware)" 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