| /linux/tools/perf/ |
| A D | builtin-ftrace.c | 347 if (!ftrace->func_irq_info) in set_tracing_func_irqinfo()
410 if (ftrace->graph_depth == 0) in set_tracing_depth()
441 if (!ftrace->inherit) in set_tracing_trace_inherit()
463 if (!ftrace->graph_noirqs) in set_tracing_funcgraph_irqs()
474 if (!ftrace->graph_verbose) in set_tracing_funcgraph_verbose()
603 if (argc && evlist__prepare_workload(ftrace->evlist, &ftrace->target, argv, false, in __cmd_ftrace()
648 if (ftrace->initial_delay) { in __cmd_ftrace()
691 reset_tracing_files(ftrace); in __cmd_ftrace()
708 ftrace->tracer = value; in perf_ftrace_config()
943 select_tracer(&ftrace); in cmd_ftrace()
[all …]
|
| /linux/tools/testing/selftests/ftrace/test.d/direct/ |
| A D | ftrace-direct.tc | 5 rmmod ftrace-direct ||:
16 rmmod ftrace-direct
23 modprobe ftrace-direct
24 rmmod ftrace-direct
29 modprobe ftrace-direct
31 rmmod ftrace-direct
34 modprobe ftrace-direct
37 rmmod ftrace-direct
40 modprobe ftrace-direct
42 rmmod ftrace-direct
[all …]
|
| A D | kprobe-direct.tc | 6 rmmod ftrace-direct ||:
7 if ! modprobe ftrace-direct ; then
17 rmmod ftrace-direct
23 modprobe ftrace-direct
29 rmmod ftrace-direct
74 modprobe ftrace-direct-too
78 rmmod ftrace-direct-too
|
| /linux/Documentation/trace/ |
| A D | boottime-trace.rst | 62 Enable given ftrace options.
64 ftrace.[instance.INSTANCE.]tracing_on = 0|1
75 ftrace.[instance.INSTANCE.]alloc_snapshot
84 ftrace.[instance.INSTANCE.]tracer = TRACER
87 ftrace.[instance.INSTANCE.]ftrace.filters
90 ftrace.[instance.INSTANCE.]ftrace.notraces
105 ftrace.[instance.INSTANCE.]event.enable
215 ftrace.event {
252 ftrace.instance {
270 ftrace {
[all …]
|
| A D | index.rst | 8 ftrace-design
10 ftrace
11 ftrace-uses
|
| A 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
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 #include <linux/ftrace.h>
108 at the start of the function where ftrace was tracing. Otherwise it
164 The ftrace FLAGS
[all …]
|
| /linux/tools/testing/ktest/examples/bootconfigs/ |
| A D | boottrace.bconf | 1 ftrace.event {
33 ftrace.instance {
36 ftrace.filters = "user_*"
45 ftrace.filters = "kernel_*"
51 ftrace.alloc_snapshot
57 ftrace = function
|
| /linux/drivers/hwtracing/stm/ |
| A 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()
50 sf->ftrace.write = stm_ftrace_write; in stm_ftrace_link()
51 sf->ftrace.flags = TRACE_EXPORT_FUNCTION | TRACE_EXPORT_EVENT in stm_ftrace_link()
54 return register_ftrace_export(&sf->ftrace); in stm_ftrace_link()
61 unregister_ftrace_export(&sf->ftrace); in stm_ftrace_unlink()
|
| /linux/samples/ftrace/ |
| A D | Makefile | 3 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT) += ftrace-direct.o
4 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT) += ftrace-direct-too.o
5 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT) += ftrace-direct-modify.o
6 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT_MULTI) += ftrace-direct-multi.o
7 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT_MULTI) += ftrace-direct-multi-modify.o
|
| /linux/tools/testing/selftests/ftrace/test.d/trigger/ |
| A D | trigger-trace-marker-synthetic.tc | 15 echo 'hist:keys=common_pid:ts0=common_timestamp.usecs if buf == "start"' > events/ftrace/print/trig…
16 …tamp.usecs-$ts0:onmatch(ftrace.print).latency($lat) if buf == "end"' >> events/ftrace/print/trigger
21 cnt=`grep 'hitcount: *1$' events/ftrace/print/hist | wc -l`
|
| A D | trigger-trace-marker-hist.tc | 14 echo 'hist:keys=common_pid' > events/ftrace/print/trigger
16 grep 'hitcount: *10$' events/ftrace/print/hist > /dev/null || \
|
| A D | trigger-trace-marker-synthetic-kernel.tc | 16 …ommon_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($lat)' > events/ftrace/print/trigger
21 grep 'hitcount: *1$' events/ftrace/print/hist > /dev/null || \
|
| /linux/tools/perf/Documentation/ |
| A 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/arch/powerpc/kernel/trace/ |
| A D | Makefile | 18 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
19 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
20 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
|
| /linux/tools/lib/traceevent/Documentation/ |
| A D | libtraceevent-parse_event.txt | 48 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/samples/ |
| A D | Makefile | 24 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT) += ftrace/
25 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT_MULTI) += ftrace/
26 obj-$(CONFIG_SAMPLE_TRACE_ARRAY) += ftrace/
|
| /linux/arch/sh/kernel/ |
| A 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/Documentation/features/debug/kprobes-on-ftrace/ |
| A D | arch-support.txt | 2 # Feature name: kprobes-on-ftrace
4 # description: arch supports combined kprobes and ftrace live patching
|
| /linux/Documentation/livepatch/ |
| A D | livepatch.rst | 43 Most of these problems are solved by using the dynamic ftrace framework as
44 a base. A Kprobe is registered as a ftrace handler when the function entry
339 The right implementation is selected by the ftrace handler, see
356 the ftrace handler is unregistered and the struct klp_ops is
415 Livepatch is based on the dynamic ftrace. In particular, functions
416 implementing ftrace or the livepatch ftrace handler could not be
432 the ftrace handler. This operation has to be reverted on return.
433 Fortunately, the generic ftrace code has the same problem and all
434 this is handled on the ftrace level.
437 - Kretprobes using the ftrace framework conflict with the patched
[all …]
|
| /linux/tools/power/pm-graph/config/ |
| A 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)
|
| A 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)
|
| A 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)
|
| A 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)
|
| /linux/tools/bootconfig/scripts/ |
| A D | bconf2ftrace.sh | 66 . `dirname $0`/ftrace.sh
258 set_array_of ${instance}.ftrace.filters \
260 set_array_of ${instance}.ftrace.notrace \
|
| /linux/tools/power/pm-graph/ |
| A D | README | 106 patch must be applied to enable ftrace data:
141 files in subdirectory: suspend-mmddyy-HHMMSS. The ftrace file can
146 raw ftrace output: <hostname>_<mode>_ftrace.txt
269 dmesg and ftrace logs. This will require a significant amount of time if
547 to set them in ftrace. It will then print out success or fail for you.
559 is ftrace supported: YES
616 ftrace : supported
635 ftrace out : /mnt/shell/emulated/0/ftrace.txt
649 # (required) get the ftrace data, this is the most important piece
650 host%> adb pull /sdcard/ftrace.txt
[all …]
|