diff options
author | Steven Rostedt <rostedt@goodmis.org> | 2014-02-10 23:38:46 -0500 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2014-02-20 12:32:54 -0500 |
commit | e1e232ca6b8faa210e5509f17d55519b4392524f (patch) | |
tree | b3666a291ab4a5dba1cf08ba058fcda904ef7591 /kernel/trace/trace_functions_graph.c | |
parent | 43fe98913c9f67e3b523615ee3316f9520a623e0 (diff) | |
download | linux-e1e232ca6b8faa210e5509f17d55519b4392524f.tar.bz2 |
tracing: Add trace_clock=<clock> kernel parameter
Being able to change the trace clock at boot can be advantageous if
you need a better source of when things happen across CPUs. The default
trace clock is the fastest, but it uses local clocks which may not be
synced across CPUs and it does not let you know when events took place
with respect to events on other CPUs.
The global trace clock can help in this case, and if you do not care
about timings, the counter "clock" is the best, as that is just a simple
atomic counter that is incremented for every event.
Usage is to add "trace_clock=counter" on the kernel command line. You
can replace counter with "global" or any of the clocks listed in
/sys/kernel/debug/tracing/trace_clock
Suggested-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Appreciated-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_functions_graph.c')
0 files changed, 0 insertions, 0 deletions