Commit | Line | Data |
---|---|---|
16444a8a ACM |
1 | # |
2 | # Architectures that offer an FTRACE implementation should select HAVE_FTRACE: | |
3 | # | |
2a3a4f66 FW |
4 | |
5 | config NOP_TRACER | |
6 | bool | |
7 | ||
16444a8a ACM |
8 | config HAVE_FTRACE |
9 | bool | |
2a3a4f66 | 10 | select NOP_TRACER |
bc0c38d1 | 11 | |
677aa9f7 SR |
12 | config HAVE_DYNAMIC_FTRACE |
13 | bool | |
14 | ||
8da3821b SR |
15 | config HAVE_FTRACE_MCOUNT_RECORD |
16 | bool | |
17 | ||
352ad25a SR |
18 | config TRACER_MAX_TRACE |
19 | bool | |
20 | ||
bc0c38d1 SR |
21 | config TRACING |
22 | bool | |
23 | select DEBUG_FS | |
86387f7e | 24 | select STACKTRACE |
5f87f112 | 25 | select TRACEPOINTS |
bc0c38d1 | 26 | |
1b29b018 SR |
27 | config FTRACE |
28 | bool "Kernel Function Tracer" | |
694379e9 | 29 | depends on HAVE_FTRACE |
d3ee6d99 | 30 | depends on DEBUG_KERNEL |
1b29b018 SR |
31 | select FRAME_POINTER |
32 | select TRACING | |
35e8e302 | 33 | select CONTEXT_SWITCH_TRACER |
1b29b018 SR |
34 | help |
35 | Enable the kernel to trace every kernel function. This is done | |
36 | by using a compiler feature to insert a small, 5-byte No-Operation | |
37 | instruction to the beginning of every kernel function, which NOP | |
38 | sequence is then dynamically patched into a tracer call when | |
39 | tracing is enabled by the administrator. If it's runtime disabled | |
40 | (the bootup default), then the overhead of the instructions is very | |
41 | small and not measurable even in micro-benchmarks. | |
35e8e302 | 42 | |
81d68a96 SR |
43 | config IRQSOFF_TRACER |
44 | bool "Interrupts-off Latency Tracer" | |
45 | default n | |
46 | depends on TRACE_IRQFLAGS_SUPPORT | |
47 | depends on GENERIC_TIME | |
c1d2327b | 48 | depends on HAVE_FTRACE |
d3ee6d99 | 49 | depends on DEBUG_KERNEL |
81d68a96 SR |
50 | select TRACE_IRQFLAGS |
51 | select TRACING | |
52 | select TRACER_MAX_TRACE | |
53 | help | |
54 | This option measures the time spent in irqs-off critical | |
55 | sections, with microsecond accuracy. | |
56 | ||
57 | The default measurement method is a maximum search, which is | |
58 | disabled by default and can be runtime (re-)started | |
59 | via: | |
60 | ||
61 | echo 0 > /debugfs/tracing/tracing_max_latency | |
62 | ||
6cd8a4bb SR |
63 | (Note that kernel size and overhead increases with this option |
64 | enabled. This option and the preempt-off timing option can be | |
65 | used together or separately.) | |
66 | ||
67 | config PREEMPT_TRACER | |
68 | bool "Preemption-off Latency Tracer" | |
69 | default n | |
70 | depends on GENERIC_TIME | |
71 | depends on PREEMPT | |
c1d2327b | 72 | depends on HAVE_FTRACE |
d3ee6d99 | 73 | depends on DEBUG_KERNEL |
6cd8a4bb SR |
74 | select TRACING |
75 | select TRACER_MAX_TRACE | |
76 | help | |
77 | This option measures the time spent in preemption off critical | |
78 | sections, with microsecond accuracy. | |
79 | ||
80 | The default measurement method is a maximum search, which is | |
81 | disabled by default and can be runtime (re-)started | |
82 | via: | |
83 | ||
84 | echo 0 > /debugfs/tracing/tracing_max_latency | |
85 | ||
86 | (Note that kernel size and overhead increases with this option | |
87 | enabled. This option and the irqs-off timing option can be | |
88 | used together or separately.) | |
89 | ||
f06c3810 IM |
90 | config SYSPROF_TRACER |
91 | bool "Sysprof Tracer" | |
4d2df795 | 92 | depends on X86 |
f06c3810 IM |
93 | select TRACING |
94 | help | |
95 | This tracer provides the trace needed by the 'Sysprof' userspace | |
96 | tool. | |
97 | ||
352ad25a SR |
98 | config SCHED_TRACER |
99 | bool "Scheduling Latency Tracer" | |
c1d2327b | 100 | depends on HAVE_FTRACE |
d3ee6d99 | 101 | depends on DEBUG_KERNEL |
352ad25a SR |
102 | select TRACING |
103 | select CONTEXT_SWITCH_TRACER | |
104 | select TRACER_MAX_TRACE | |
105 | help | |
106 | This tracer tracks the latency of the highest priority task | |
107 | to be scheduled in, starting from the point it has woken up. | |
108 | ||
35e8e302 SR |
109 | config CONTEXT_SWITCH_TRACER |
110 | bool "Trace process context switches" | |
c1d2327b | 111 | depends on HAVE_FTRACE |
d3ee6d99 | 112 | depends on DEBUG_KERNEL |
35e8e302 SR |
113 | select TRACING |
114 | select MARKERS | |
115 | help | |
116 | This tracer gets called from the context switch and records | |
117 | all switching of tasks. | |
118 | ||
e5a81b62 SR |
119 | config STACK_TRACER |
120 | bool "Trace max stack" | |
121 | depends on HAVE_FTRACE | |
2ff01c6a | 122 | depends on DEBUG_KERNEL |
e5a81b62 SR |
123 | select FTRACE |
124 | select STACKTRACE | |
125 | help | |
126 | This tracer records the max stack of the kernel, and displays | |
127 | it in debugfs/tracing/stack_trace | |
128 | ||
3d083395 SR |
129 | config DYNAMIC_FTRACE |
130 | bool "enable/disable ftrace tracepoints dynamically" | |
131 | depends on FTRACE | |
677aa9f7 | 132 | depends on HAVE_DYNAMIC_FTRACE |
d3ee6d99 | 133 | depends on DEBUG_KERNEL |
3d083395 SR |
134 | default y |
135 | help | |
136 | This option will modify all the calls to ftrace dynamically | |
137 | (will patch them out of the binary image and replaces them | |
138 | with a No-Op instruction) as they are called. A table is | |
139 | created to dynamically enable them again. | |
140 | ||
141 | This way a CONFIG_FTRACE kernel is slightly larger, but otherwise | |
142 | has native performance as long as no tracing is active. | |
143 | ||
144 | The changes to the code are done by a kernel thread that | |
145 | wakes up once a second and checks to see if any ftrace calls | |
146 | were made. If so, it runs stop_machine (stops all CPUS) | |
147 | and modifies the code to jump over the call to ftrace. | |
60a11774 | 148 | |
8da3821b SR |
149 | config FTRACE_MCOUNT_RECORD |
150 | def_bool y | |
151 | depends on DYNAMIC_FTRACE | |
152 | depends on HAVE_FTRACE_MCOUNT_RECORD | |
153 | ||
60a11774 SR |
154 | config FTRACE_SELFTEST |
155 | bool | |
156 | ||
157 | config FTRACE_STARTUP_TEST | |
158 | bool "Perform a startup test on ftrace" | |
159 | depends on TRACING | |
d3ee6d99 | 160 | depends on DEBUG_KERNEL |
60a11774 SR |
161 | select FTRACE_SELFTEST |
162 | help | |
163 | This option performs a series of startup tests on ftrace. On bootup | |
164 | a series of tests are made to verify that the tracer is | |
165 | functioning properly. It will do tests on all the configured | |
166 | tracers of ftrace. |