aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py
diff options
context:
space:
mode:
authorSteven J. Magnani <[email protected]>2010-04-02 18:29:39 +0000
committerMichal Simek <[email protected]>2010-04-07 05:27:25 +0000
commitd2bf98e6fc2612cbd2fc40f75a1e2c5d60262331 (patch)
tree7a69042d5f841ee7f66f0d6661df09c9fdfbe402 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py
parentMerge branch 'urgent' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/... (diff)
downloadkernel-d2bf98e6fc2612cbd2fc40f75a1e2c5d60262331.tar.gz
kernel-d2bf98e6fc2612cbd2fc40f75a1e2c5d60262331.zip
microblaze: Fix ftrace_update_ftrace_func panic
The Microblaze dynamic ftrace code assumes a call ordering that is not met in all scenarios. Specifically, executing a command similar to: echo 105 > /sys/kernel/debug/tracing/set_ftrace_pid before any other tracing-related commands results in a kernel panic: BUG: failure at arch/microblaze/kernel/ftrace.c:198/ftrace_update_ftrace_func()! Recoding ftrace_update_ftrace_func() to use &ftrace_caller directly eliminates the need to capture its address elsewhere (and thus rely on a particular call sequence). Signed-off-by: Steven J. Magnani <[email protected]> Signed-off-by: Michal Simek <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py')
0 files changed, 0 insertions, 0 deletions