diff options
author | Steven Rostedt (Red Hat) <rostedt@goodmis.org> | 2014-07-11 14:39:10 -0400 |
---|---|---|
committer | Steven Rostedt <rostedt@goodmis.org> | 2014-07-16 11:01:24 -0400 |
commit | 646d7043adf3d92de5d3db1244a82a12628303de (patch) | |
tree | 09d3ed9c379a06b0ba7ce9a2ec5173ba8a097b96 /mm | |
parent | ca65ef1ab6b498b77985b9a3f5ab12c09bbf764e (diff) |
ftrace: Allow archs to specify if they need a separate function graph trampoline
Currently if an arch supports function graph tracing, the core code will
just assign the function graph trampoline to the function graph addr that
gets called.
But as the old method for function graph tracing always calls the function
trampoline first and that calls the function graph trampoline, some
archs may have the function graph trampoline dependent on operations that
were done in the function trampoline. This causes function graph tracer
to break on those archs.
Instead of having the default be to set the function graph ftrace_ops
to the function graph trampoline, have it instead just set it to zero
which will keep it from jumping to a trampoline that is not set up
to be jumped directly too.
Link: http://lkml.kernel.org/r/53BED155.9040607@nvidia.com
Reported-by: Tuomas Tynkkynen <ttynkkynen@nvidia.com>
Tested-by: Tuomas Tynkkynen <ttynkkynen@nvidia.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions