diff options
author | Steven Rostedt (VMware) <[email protected]> | 2017-03-23 10:33:52 -0400 |
---|---|---|
committer | Thomas Gleixner <[email protected]> | 2017-03-24 10:14:07 +0100 |
commit | 644e0e8dc76b919976c44d3929164d42cbe656bc (patch) | |
tree | e11a16a3e85b3138629648d44c3dc08d6bfc18df /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | ff04b440d2d645fd8a5b3385b1b2e4d19d3fe746 (diff) |
x86/ftrace: Add -mfentry support to x86_32 with DYNAMIC_FTRACE set
x86_64 has had fentry support for some time. I did not add support to x86_32
as I was unsure if it will be used much in the future. It is still very much
used, and there's issues with function graph tracing with gcc playing around
with the mcount frames, causing function graph to panic. The fentry code
does not have this issue, and is able to cope as there is no frame to mess
up.
Note, this only adds support for fentry when DYNAMIC_FTRACE is set. There's
really no reason to not have that set, because the performance of the
machine drops significantly when it's not enabled.
Keep !DYNAMIC_FTRACE around to test it off, as there's still some archs
that have FTRACE but not DYNAMIC_FTRACE.
Signed-off-by: Steven Rostedt (VMware) <[email protected]>
Reviewed-by: Masami Hiramatsu <[email protected]>
Reviewed-by: Josh Poimboeuf <[email protected]>
Reviewed-by: Ingo Molnar <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Andy Lutomirski <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Linus Torvalds <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Thomas Gleixner <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions