diff options
author | Steven Rostedt (Google) <[email protected]> | 2023-01-24 09:56:53 -0500 |
---|---|---|
committer | Steven Rostedt (Google) <[email protected]> | 2023-03-21 14:00:10 -0400 |
commit | e11b521a7b69c2621bb2e5920bb96f6d2facdc7e (patch) | |
tree | 9c56b9fb5c5536911e206cf8466d4afac640b77f /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py | |
parent | 8328e36da9cd8cb051394630e910cbb461f7e3ec (diff) |
ftrace: Show a list of all functions that have ever been enabled
When debugging a crash that appears to be related to ftrace, but not for
sure, it is useful to know if a function was ever enabled by ftrace or
not. It could be that a BPF program was attached to it, or possibly a live
patch.
We are having crashes in the field where this information is not always
known. But having ftrace set a flag if a function has ever been attached
since boot up helps tremendously in trying to know if a crash had to do
with something using ftrace.
For analyzing crashes, the use of a kdump image can have access to the
flags. When looking at issues where the kernel did not panic, the
touched_functions file can simply be used.
Link: https://lore.kernel.org/linux-trace-kernel/[email protected]
Cc: Masami Hiramatsu <[email protected]>
Cc: Catalin Marinas <[email protected]>
Tested-by: Mark Rutland <[email protected]>
Tested-by: Chris Li <[email protected]>
Signed-off-by: Steven Rostedt (Google) <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/SchedGui.py')
0 files changed, 0 insertions, 0 deletions