diff options
author | 2019-08-07 12:27:30 -0400 | |
---|---|---|
committer | 2019-08-31 12:19:40 -0400 | |
commit | 58fe7a87db51ea00596187765dabfc2c4ea2b436 (patch) | |
tree | 63ef030e6f87d3519283db4f97db94cadab237ea /tools/perf/scripts/python/export-to-postgresql.py | |
parent | tracing/arm64: Have max stack tracer handle the case of return address after data (diff) | |
download | linux-dev-58fe7a87db51ea00596187765dabfc2c4ea2b436.tar.xz linux-dev-58fe7a87db51ea00596187765dabfc2c4ea2b436.zip |
tracing: Document the stack trace algorithm in the comments
As the max stack tracer algorithm is not that easy to understand from the
code, add comments that explain the algorithm and mentions how
ARCH_FTRACE_SHIFT_STACK_TRACER affects it.
Link: http://lkml.kernel.org/r/20190806123455.487ac02b@gandalf.local.home
Suggested-by: Joel Fernandes <joel@joelfernandes.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions