| /Linux-v4.19/tools/perf/ |
| D | builtin-ftrace.c | 131 static int reset_tracing_files(struct perf_ftrace *ftrace __maybe_unused) in reset_tracing_files()
152 static int set_tracing_pid(struct perf_ftrace *ftrace) in set_tracing_pid() argument
157 if (target__has_cpu(&ftrace->target)) in set_tracing_pid()
160 for (i = 0; i < thread_map__nr(ftrace->evlist->threads); i++) { in set_tracing_pid()
162 ftrace->evlist->threads->map[i]); in set_tracing_pid()
194 static int set_tracing_cpu(struct perf_ftrace *ftrace) in set_tracing_cpu() argument
196 struct cpu_map *cpumap = ftrace->evlist->cpus; in set_tracing_cpu()
198 if (!target__has_cpu(&ftrace->target)) in set_tracing_cpu()
226 static int set_tracing_filters(struct perf_ftrace *ftrace) in set_tracing_filters() argument
230 ret = __set_tracing_filter("set_ftrace_filter", &ftrace->filters); in set_tracing_filters()
[all …]
|
| /Linux-v4.19/tools/testing/selftests/ftrace/test.d/trigger/ |
| D | trigger-trace-marker-synthetic.tc | 29 if [ ! -d events/ftrace/print ]; then
34 if [ ! -f events/ftrace/print/trigger ]; then
39 if [ ! -f events/ftrace/print/hist ]; then
49 echo 'hist:keys=common_pid:ts0=common_timestamp.usecs if buf == "start"' > events/ftrace/print/trig…
50 …tamp.usecs-$ts0:onmatch(ftrace.print).latency($lat) if buf == "end"' >> events/ftrace/print/trigger
55 cnt=`grep 'hitcount: *1$' events/ftrace/print/hist | wc -l`
|
| D | trigger-trace-marker-hist.tc | 23 if [ ! -d events/ftrace/print ]; then
28 if [ ! -f events/ftrace/print/trigger ]; then
33 if [ ! -f events/ftrace/print/hist ]; then
42 echo 'hist:keys=common_pid' > events/ftrace/print/trigger
44 grep 'hitcount: *10$' events/ftrace/print/hist > /dev/null || \
|
| D | trigger-trace-marker-synthetic-kernel.tc | 29 if [ ! -d events/ftrace/print ]; then
39 if [ ! -f events/ftrace/print/trigger ]; then
44 if [ ! -f events/ftrace/print/hist ]; then
55 …ommon_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($lat)' > events/ftrace/print/trigger
60 grep 'hitcount: *1$' events/ftrace/print/hist > /dev/null || \
|
| D | trigger-trace-marker-snapshot.tc | 29 if [ ! -d events/ftrace/print ]; then
34 if [ ! -f events/ftrace/print/trigger ]; then
61 echo 'snapshot' > events/ftrace/print/trigger
|
| /Linux-v4.19/drivers/hwtracing/stm/ |
| D | ftrace.c | 21 struct trace_export ftrace; member
39 struct stm_ftrace *stm = container_of(export, struct stm_ftrace, ftrace); in stm_ftrace_write()
48 sf->ftrace.write = stm_ftrace_write; in stm_ftrace_link()
50 return register_ftrace_export(&sf->ftrace); in stm_ftrace_link()
57 unregister_ftrace_export(&sf->ftrace); in stm_ftrace_unlink()
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf-ftrace.txt | 1 perf-ftrace(1)
6 perf-ftrace - simple wrapper for kernel's ftrace functionality
12 'perf ftrace' <command>
16 The 'perf ftrace' command is a simple wrapper of kernel's ftrace
20 The following options apply to perf ftrace.
|
| /Linux-v4.19/Documentation/trace/ |
| D | index.rst | 8 ftrace-design
10 ftrace
11 ftrace-uses
|
| D | ftrace-uses.rst | 2 Using ftrace to hook to functions
15 The ftrace infrastructure was originally created to attach callbacks to the
19 how to use ftrace to implement your own function callbacks.
22 The ftrace context
33 The ftrace infrastructure has some protections against recursions and RCU
41 is used to tell ftrace what function should be called as the callback
43 ftrace to handle.
46 an ftrace_ops with ftrace:
68 .. c:function:: #include <linux/ftrace.h>
108 at the start of the function where ftrace was tracing. Otherwise it
[all …]
|
| /Linux-v4.19/arch/powerpc/kernel/trace/ |
| D | Makefile | 20 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
21 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
22 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
|
| /Linux-v4.19/arch/sh/kernel/ |
| D | Makefile | 41 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
42 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
43 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /Linux-v4.19/Documentation/features/debug/kprobes-on-ftrace/ |
| D | arch-support.txt | 2 # Feature name: kprobes-on-ftrace
4 # description: arch supports combined kprobes and ftrace live patching
|
| /Linux-v4.19/arch/parisc/kernel/ |
| D | Makefile | 33 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o
34 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /Linux-v4.19/kernel/trace/ |
| D | Kconfig | 15 See Documentation/trace/ftrace-design.rst
20 See Documentation/trace/ftrace-design.rst
25 See Documentation/trace/ftrace-design.rst
30 See Documentation/trace/ftrace-design.rst
38 See Documentation/trace/ftrace-design.rst
43 See Documentation/trace/ftrace-design.rst
304 ftrace interface, e.g.:
450 Tracing also is possible using the ftrace interface, e.g.:
467 on the fly via the ftrace interface. See
482 This is only for the developers who want to debug ftrace itself
[all …]
|
| /Linux-v4.19/tools/power/pm-graph/config/ |
| D | freeze.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | standby.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | freeze-callgraph.cfg | 26 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
34 # add the dmesg and ftrace log to the html output (default: false)
77 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | freeze-dev.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | standby-callgraph.cfg | 26 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
34 # add the dmesg and ftrace log to the html output (default: false)
77 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | suspend-dev.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | suspend-x2-proc.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | standby-dev.cfg | 25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
33 # add the dmesg and ftrace log to the html output (default: false)
76 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| D | suspend-callgraph.cfg | 26 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
34 # add the dmesg and ftrace log to the html output (default: false)
77 # gather detailed ftrace callgraph data on all timeline events (default: false)
|
| /Linux-v4.19/tools/testing/selftests/ftrace/ |
| D | README | 3 This is a collection of testcases for ftrace tracing feature in the Linux
4 kernel. Since ftrace exports interfaces via the debugfs, we just need
7 Running the ftrace testcases
|
| /Linux-v4.19/arch/arm/kernel/ |
| D | Makefile | 51 obj-$(CONFIG_FUNCTION_TRACER) += entry-ftrace.o
52 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o insn.o
53 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o insn.o
|
