Home
last modified time | relevance | path

Searched refs:ftrace (Results 1 – 25 of 94) sorted by relevance

1234

/Linux-v5.4/tools/perf/
Dbuiltin-ftrace.c133 static int reset_tracing_files(struct perf_ftrace *ftrace __maybe_unused) in reset_tracing_files()
154 static int set_tracing_pid(struct perf_ftrace *ftrace) in set_tracing_pid() argument
159 if (target__has_cpu(&ftrace->target)) in set_tracing_pid()
162 for (i = 0; i < perf_thread_map__nr(ftrace->evlist->core.threads); i++) { in set_tracing_pid()
164 ftrace->evlist->core.threads->map[i]); in set_tracing_pid()
196 static int set_tracing_cpu(struct perf_ftrace *ftrace) in set_tracing_cpu() argument
198 struct perf_cpu_map *cpumap = ftrace->evlist->core.cpus; in set_tracing_cpu()
200 if (!target__has_cpu(&ftrace->target)) in set_tracing_cpu()
228 static int set_tracing_filters(struct perf_ftrace *ftrace) in set_tracing_filters() argument
232 ret = __set_tracing_filter("set_ftrace_filter", &ftrace->filters); in set_tracing_filters()
[all …]
/Linux-v5.4/tools/testing/selftests/ftrace/test.d/trigger/
Dtrigger-trace-marker-synthetic.tc21 if [ ! -d events/ftrace/print ]; then
26 if [ ! -f events/ftrace/print/trigger ]; then
31 if [ ! -f events/ftrace/print/hist ]; then
39 echo 'hist:keys=common_pid:ts0=common_timestamp.usecs if buf == "start"' > events/ftrace/print/trig…
40 …tamp.usecs-$ts0:onmatch(ftrace.print).latency($lat) if buf == "end"' >> events/ftrace/print/trigger
45 cnt=`grep 'hitcount: *1$' events/ftrace/print/hist | wc -l`
Dtrigger-trace-marker-hist.tc16 if [ ! -d events/ftrace/print ]; then
21 if [ ! -f events/ftrace/print/trigger ]; then
26 if [ ! -f events/ftrace/print/hist ]; then
33 echo 'hist:keys=common_pid' > events/ftrace/print/trigger
35 grep 'hitcount: *10$' events/ftrace/print/hist > /dev/null || \
Dtrigger-trace-marker-synthetic-kernel.tc21 if [ ! -d events/ftrace/print ]; then
31 if [ ! -f events/ftrace/print/trigger ]; then
36 if [ ! -f events/ftrace/print/hist ]; then
45 …ommon_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($lat)' > events/ftrace/print/trigger
50 grep 'hitcount: *1$' events/ftrace/print/hist > /dev/null || \
Dtrigger-trace-marker-snapshot.tc21 if [ ! -d events/ftrace/print ]; then
26 if [ ! -f events/ftrace/print/trigger ]; then
51 echo 'snapshot' > events/ftrace/print/trigger
/Linux-v5.4/drivers/hwtracing/stm/
Dftrace.c21 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-v5.4/tools/perf/Documentation/
Dperf-ftrace.txt1 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-v5.4/Documentation/trace/
Dindex.rst8 ftrace-design
10 ftrace
11 ftrace-uses
Dftrace-uses.rst2 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-v5.4/arch/powerpc/kernel/trace/
DMakefile18 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
19 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
20 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
/Linux-v5.4/tools/lib/traceevent/Documentation/
Dlibtraceevent-parse_event.txt48 buf = read_file("/sys/kernel/tracing/events/ftrace/print/format", &size);
49 if (tep_parse_event(tep, buf, size, "ftrace") != 0) {
50 /* Failed to parse the ftrace print format */
53 if (tep_parse_format(tep, &event, buf, size, "ftrace") != 0) {
54 /* Failed to parse the ftrace print format */
/Linux-v5.4/arch/sh/kernel/
DMakefile41 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
42 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
43 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
/Linux-v5.4/Documentation/features/debug/kprobes-on-ftrace/
Darch-support.txt2 # Feature name: kprobes-on-ftrace
4 # description: arch supports combined kprobes and ftrace live patching
/Linux-v5.4/kernel/trace/
DKconfig16 See Documentation/trace/ftrace-design.rst
21 See Documentation/trace/ftrace-design.rst
26 See Documentation/trace/ftrace-design.rst
31 See Documentation/trace/ftrace-design.rst
39 See Documentation/trace/ftrace-design.rst
44 See Documentation/trace/ftrace-design.rst
305 ftrace interface, e.g.:
452 Tracing also is possible using the ftrace interface, e.g.:
470 on the fly via the ftrace interface. See
485 This is only for the developers who want to debug ftrace itself
[all …]
/Linux-v5.4/tools/power/pm-graph/
DREADME49 and will capture dmesg and ftrace data. This data is transformed into a set of
100 patch must be applied to enable ftrace data:
135 files in subdirectory: suspend-mmddyy-HHMMSS. The ftrace file can
140 raw ftrace output: <hostname>_<mode>_ftrace.txt
257 # Add Logs: add the dmesg and ftrace log to the html output (def: false)
287 # Callgraph: gather ftrace callgraph data on all timeline events (def: false)
443 to set them in ftrace. It will then print out success or fail for you.
455 is ftrace supported: YES
490 script on the device, then pull the ftrace log back to the host and run
512 ftrace : supported
[all …]
/Linux-v5.4/tools/power/pm-graph/config/
Dfreeze.cfg25 # 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)
Dstandby.cfg25 # 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)
Dfreeze-dev.cfg25 # 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)
Dstandby-callgraph.cfg26 # 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)
Dstandby-dev.cfg25 # 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)
Dsuspend-callgraph.cfg26 # 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)
Dsuspend-dev.cfg25 # 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)
/Linux-v5.4/Documentation/livepatch/
Dlivepatch.rst56 Most of these problems are solved by using the dynamic ftrace framework as
57 a base. A Kprobe is registered as a ftrace handler when the function entry
59 a live patch is called with the help of a custom ftrace handler. But there are
340 ftrace handler is registered\ [#]_. This stage is indicated by a value of '1'
349 Note that functions might be patched multiple times. The ftrace handler
352 The right implementation is selected by the ftrace handler, see
369 the ftrace handler is unregistered and the struct klp_ops is
391 patch are removed from the corresponding struct klp_ops. The ftrace handler
428 Livepatch is based on the dynamic ftrace. In particular, functions
429 implementing ftrace or the livepatch ftrace handler could not be
[all …]
/Linux-v5.4/arch/parisc/kernel/
DMakefile35 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o
36 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
/Linux-v5.4/arch/arm/kernel/
DMakefile51 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

1234