Creation of the initcall tracer
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | Tracing/ftrace: Add the initcall tracerinclude/ kernel/ kernel/ | +124 | 0 replies | |
| 2/4 | Tracing/ftrace: Make tracing suitable to run the initcall tracerkernel/ | +10 | 0 replies | |
| 3/4 | Tracing/ftrace: Give an entry on the config for initcall tracerkernel/ kernel/ | +11 | 0 replies | |
| 4/4 | Tracing/ftrace: Launch initcall tracing after pre-smp initcalls.init/ | +9 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Patch -tip 0/4] Creation of the initcall tracer
This patchset is about the initcall tracer requested by Ingo Molnar.
It is supposed to replace the printk involved during fastboot if the initcall_debug parameter has been selected.
Currently this tracer is a test. Its output is not yet adapted for scripts/bootgraph.pl which uses the old initcalls printk to produce a graph. But since this tracer will output sched_switch and stack_trace, we should first talk about the future output format of this tracer in sync with bootgraph.pl
It currently not uses the sched_switch and stack_trace tracers since related functions of insertion into the ring buffer perhaps need first to be moved on their own tracer file. But it have to be discussed.
Note that you need the initcall_debug to enable this tracer. When printk from initcall_debug will disappear, we could surely enable this tracer by default without this parameter.
Old printk have been kept for backward compatibility.
Please don't hesitate to give any comment.
Thanks.
Frédéric Weisbecker.