Home
last modified time | relevance | path

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

12345

/kernel/linux/linux-5.10/tools/perf/
Dbuiltin-ftrace.c245 static void reset_tracing_options(struct perf_ftrace *ftrace __maybe_unused) in reset_tracing_options()
257 static int reset_tracing_files(struct perf_ftrace *ftrace __maybe_unused) in reset_tracing_files()
278 reset_tracing_options(ftrace); in reset_tracing_files()
282 static int set_tracing_pid(struct perf_ftrace *ftrace) in set_tracing_pid() argument
287 if (target__has_cpu(&ftrace->target)) in set_tracing_pid()
290 for (i = 0; i < perf_thread_map__nr(ftrace->evlist->core.threads); i++) { in set_tracing_pid()
292 perf_thread_map__pid(ftrace->evlist->core.threads, i)); in set_tracing_pid()
324 static int set_tracing_cpu(struct perf_ftrace *ftrace) in set_tracing_cpu() argument
326 struct perf_cpu_map *cpumap = ftrace->evlist->core.cpus; in set_tracing_cpu()
328 if (!target__has_cpu(&ftrace->target)) in set_tracing_cpu()
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/direct/
Dftrace-direct.tc5 rmmod ftrace-direct ||:
6 if ! modprobe ftrace-direct ; then
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
[all …]
Dkprobe-direct.tc6 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
/kernel/linux/linux-5.10/Documentation/trace/
Dboottime-trace.rst13 device initialization with full features of ftrace including per-event
23 boot config file [1]_. All options are under "ftrace." or "kernel."
40 Dump ftrace on Oops. If MODE = 1 or omitted, dump trace buffer
59 These options can be used for each instance including global ftrace node.
61 ftrace.[instance.INSTANCE.]options = OPT1[, OPT2[...]]
62 Enable given ftrace options.
64 ftrace.[instance.INSTANCE.]tracing_on = 0|1
68 ftrace.[instance.INSTANCE.]trace_clock = CLOCK
69 Set given CLOCK to ftrace's trace_clock.
71 ftrace.[instance.INSTANCE.]buffer_size = SIZE
[all …]
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 #include <linux/ftrace.h>
108 at the start of the function where ftrace was tracing. Otherwise it
[all …]
/kernel/linux/linux-5.10/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()
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()
/kernel/linux/linux-5.10/samples/ftrace/
DMakefile3 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
/kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/trigger/
Dtrigger-trace-marker-synthetic.tc15 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`
Dtrigger-trace-marker-hist.tc14 echo 'hist:keys=common_pid' > events/ftrace/print/trigger
16 grep 'hitcount: *10$' events/ftrace/print/hist > /dev/null || \
Dtrigger-trace-marker-synthetic-kernel.tc16 …ommon_timestamp.usecs-$ts0:onmatch(sched.sched_waking).latency($lat)' > events/ftrace/print/trigger
21 grep 'hitcount: *1$' events/ftrace/print/hist > /dev/null || \
/kernel/linux/linux-5.10/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
/kernel/linux/build/test/moduletest/runtest/bin/cpuisolation_t/testcases/bin/
Dcpuisolation05.sh47 workq ability > cputrace.ftrace &
61 cat cputrace.ftrace | grep "set_busy" &&
62 cat cputrace.ftrace | grep "update_nr_need"
65 rm -rf cputrace.ftrace
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-5.10/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 */
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/Documentation/features/debug/kprobes-on-ftrace/
Darch-support.txt2 # Feature name: kprobes-on-ftrace
4 # description: arch supports combined kprobes and ftrace live patching
/kernel/linux/linux-5.10/tools/bootconfig/scripts/
Dbconf2ftrace.sh66 . `dirname $0`/ftrace.sh
157 set_array_of ${instance}.ftrace.filters \
159 set_array_of ${instance}.ftrace.notrace \
/kernel/linux/linux-5.10/samples/
DMakefile22 obj-$(CONFIG_SAMPLE_FTRACE_DIRECT) += ftrace/
23 obj-$(CONFIG_SAMPLE_TRACE_ARRAY) += ftrace/
/kernel/linux/linux-5.10/tools/power/pm-graph/config/
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.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.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)
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/arch/parisc/kernel/
DMakefile35 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o
36 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
/kernel/linux/linux-5.10/kernel/trace/
DKconfig16 See Documentation/trace/ftrace-design.rst
21 See Documentation/trace/ftrace-design.rst
26 See Documentation/trace/ftrace-design.rst
37 See Documentation/trace/ftrace-design.rst
42 See Documentation/trace/ftrace-design.rst
139 Enable developer to setup ftrace subsystem via supplemental
184 compile time, a table is made of all the locations that ftrace
382 ftrace interface, e.g.:
504 Tracing also is possible using the ftrace interface, e.g.:
522 on the fly via the ftrace interface. See
[all …]

12345