| /linux-4.1.27/arch/blackfin/kernel/ |
| D | Makefile | 20 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
21 obj-$(CONFIG_FUNCTION_TRACER) += ftrace-entry.o
22 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /linux-4.1.27/arch/sh/kernel/ |
| D | Makefile | 40 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
41 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
42 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /linux-4.1.27/arch/parisc/kernel/ |
| D | Makefile | 36 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o
37 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /linux-4.1.27/arch/arm/kernel/ |
| D | Makefile | 48 obj-$(CONFIG_FUNCTION_TRACER) += entry-ftrace.o
49 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o insn.o
50 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o insn.o
|
| /linux-4.1.27/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-4.1.27/arch/arm64/kernel/ |
| D | Makefile | 25 arm64-obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o entry-ftrace.o
|
| /linux-4.1.27/kernel/trace/ |
| D | Kconfig | 15 See Documentation/trace/ftrace-design.txt
20 See Documentation/trace/ftrace-design.txt
25 See Documentation/trace/ftrace-design.txt
30 See Documentation/trace/ftrace-design.txt
35 See Documentation/trace/ftrace-design.txt
43 See Documentation/trace/ftrace-design.txt
48 See Documentation/trace/ftrace-design.txt
246 ftrace interface, e.g.:
392 Tracing also is possible using the ftrace interface, e.g.:
409 on the fly via the ftrace interface. See
[all …]
|
| D | Makefile | 70 libftrace-y := ftrace.o
|
| D | trace_export.c | 17 #define TRACE_SYSTEM ftrace
|
| D | ftrace.c | 1109 # error Dynamic ftrace depends on MCOUNT_RECORD
|
| /linux-4.1.27/arch/x86/kernel/kprobes/ |
| D | Makefile | 7 obj-$(CONFIG_KPROBES_ON_FTRACE) += ftrace.o
|
| /linux-4.1.27/arch/x86/kernel/ |
| D | Makefile | 70 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
72 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
73 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace-design.txt | 14 ftrace.txt file.
17 their kernel should make it all the way to dynamic ftrace support.
109 mcount function to check ftrace graph function pointers, as well as implement
230 this arch, define ARCH_HAS_SYSCALL_MATCH_SYM_NAME in asm/ftrace.h and
241 This option doesn't make much sense without also implementing dynamic ftrace.
251 - asm/ftrace.h:
266 First you will need to fill out some arch details in your asm/ftrace.h.
289 did already create a mcount() function earlier, dynamic ftrace only wants a
345 linux/ftrace.h for the functions:
363 The function grapher needs a few tweaks in order to work with dynamic ftrace.
|
| D | ftrace.txt | 1 ftrace - Function Tracer
21 Although ftrace is typically considered the function tracer, it
27 One of the most common uses of ftrace is the event tracing.
36 See ftrace-design.txt for details for arch porters and such.
45 When debugfs is configured into the kernel (which selecting any ftrace
60 Any selected ftrace option will also create a directory called tracing
62 the ftrace directory (cd /sys/kernel/debug/tracing) and will only concentrate
66 That's it! (assuming that you have ftrace configured into your kernel)
70 of ftrace. Here is a list of some of the key files:
184 When dynamic ftrace is configured in (see the
[all …]
|
| D | function-graph-fold.vim | 1 " Enable folding for ftrace function_graph traces.
|
| D | tracepoint-analysis.txt | 113 Documentation/trace/ftrace.txt describes how to enable events on a per-thread
137 Documentation/trace/ftrace.txt covers in-depth how to filter events in
138 ftrace. Obviously using grep and awk of trace_pipe is an option as well
|
| D | mmiotrace.txt | 18 ftrace framework by Pekka Paalanen <pq@iki.fi>.
|
| D | events.txt | 322 set_ftrace_filter 'ftrace filter commands' (see the 'Filter commands'
323 section of Documentation/trace/ftrace.txt), but there are major
|
| /linux-4.1.27/fs/pstore/ |
| D | Makefile | 8 obj-$(CONFIG_PSTORE_FTRACE) += ftrace.o
|
| /linux-4.1.27/scripts/ |
| D | recordmcount.c | 448 const char ftrace[] = "/ftrace.o"; in main() local
449 int ftrace_size = sizeof(ftrace) - 1; in main()
483 strcmp(file + (len - ftrace_size), ftrace) == 0) in main()
|
| /linux-4.1.27/arch/powerpc/kernel/ |
| D | Makefile | 118 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
119 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
120 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
|
| /linux-4.1.27/arch/sparc/kernel/ |
| D | Makefile | 93 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
94 obj-$(CONFIG_FUNCTION_GRAPH_TRACER) += ftrace.o
|
| /linux-4.1.27/arch/microblaze/kernel/ |
| D | Makefile | 29 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o mcount.o
|
| /linux-4.1.27/arch/metag/kernel/ |
| D | Makefile | 32 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
|
| /linux-4.1.27/arch/um/include/asm/ |
| D | Kbuild | 10 generic-y += ftrace.h
|
| /linux-4.1.27/arch/mips/kernel/ |
| D | Makefile | 36 obj-$(CONFIG_FTRACE_SYSCALLS) += ftrace.o
37 obj-$(CONFIG_FUNCTION_TRACER) += mcount.o ftrace.o
|
| /linux-4.1.27/arch/tile/kernel/ |
| D | Makefile | 32 obj-$(CONFIG_FUNCTION_TRACER) += ftrace.o mcount_64.o
|
| /linux-4.1.27/tools/testing/selftests/ |
| D | Makefile | 6 TARGETS += ftrace
|
| /linux-4.1.27/arch/s390/kernel/ |
| D | Makefile | 51 obj-$(CONFIG_FUNCTION_TRACER) += mcount.o ftrace.o
|
| /linux-4.1.27/arch/arc/include/asm/ |
| D | Kbuild | 13 generic-y += ftrace.h
|
| /linux-4.1.27/arch/arm64/include/asm/ |
| D | Kbuild | 16 generic-y += ftrace.h
|
| /linux-4.1.27/arch/hexagon/include/asm/ |
| D | Kbuild | 17 generic-y += ftrace.h
|
| /linux-4.1.27/Documentation/ |
| D | ramoops.txt | 110 related hangs. The functions call chain log is stored in a "ftrace-ramoops"
118 # tail /mnt/ftrace-ramoops
|
| D | sysrq.txt | 125 'z' - Dump the ftrace buffer
|
| D | kmemcheck.txt | 78 page fault handler is called, the ftrace framework will be called
79 before kmemcheck has had a chance to handle the fault. If ftrace then
|
| D | kprobes.txt | 705 marked with [OPTIMIZED]. If the probe is ftrace-based, it is marked with
|
| D | kernel-parameters.txt | 418 Allocate the ftrace snapshot buffer on boot up when the
1147 ftrace=[tracer]
1154 If no parameter is passed, ftrace will dump
3664 See also Documentation/trace/ftrace.txt "trace options"
|
| /linux-4.1.27/arch/unicore32/include/asm/ |
| D | Kbuild | 16 generic-y += ftrace.h
|
| /linux-4.1.27/arch/nios2/include/asm/ |
| D | Kbuild | 19 generic-y += ftrace.h
|
| /linux-4.1.27/drivers/net/wireless/iwlwifi/ |
| D | Kconfig | 146 register with the ftrace framework for event tracing and dump
148 increase the ringbuffer size. See the ftrace documentation
|
| /linux-4.1.27/arch/openrisc/include/asm/ |
| D | Kbuild | 25 generic-y += ftrace.h
|
| /linux-4.1.27/arch/ia64/kernel/ |
| D | Makefile | 28 obj-$(CONFIG_DYNAMIC_FTRACE) += ftrace.o
|
| /linux-4.1.27/drivers/net/wireless/brcm80211/ |
| D | Kconfig | 76 with ftrace to dump event information into the trace ringbuffer.
|
| /linux-4.1.27/tools/virtio/virtio-trace/ |
| D | README | 96 1) Enable ftrace in the guest
|
| /linux-4.1.27/Documentation/x86/ |
| D | earlyprintk.txt | 126 …ow-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W) dump-ftrace-buffer(Z)
|
| /linux-4.1.27/Documentation/RCU/ |
| D | stallwarn.txt | 246 If you can reliably trigger the stall, ftrace can be quite helpful.
|
| /linux-4.1.27/tools/perf/ |
| D | design.txt | 144 Counters of the type PERF_TYPE_TRACEPOINT are available when the ftrace event
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 10083 F: Documentation/trace/ftrace.txt
10084 F: arch/*/*/*/ftrace.h
10085 F: arch/*/kernel/ftrace.c
10086 F: include/*/ftrace.h
10090 F: tools/testing/selftests/ftrace/
|