diff options
-rw-r--r-- | litmus/Kconfig | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/litmus/Kconfig b/litmus/Kconfig index 9fc402e79cfd..be25d7c53971 100644 --- a/litmus/Kconfig +++ b/litmus/Kconfig | |||
@@ -206,22 +206,11 @@ menu "Tracing" | |||
206 | 206 | ||
207 | config FEATHER_TRACE | 207 | config FEATHER_TRACE |
208 | bool "Feather-Trace Infrastructure" | 208 | bool "Feather-Trace Infrastructure" |
209 | depends on !RELOCATABLE | ||
210 | default y | 209 | default y |
211 | help | 210 | help |
212 | Feather-Trace basic tracing infrastructure. Includes device file | 211 | Feather-Trace basic tracing infrastructure. Includes device file |
213 | driver and instrumentation point support. | 212 | driver and instrumentation point support. |
214 | 213 | ||
215 | There are actually two implementations of Feather-Trace. | ||
216 | 1) A slower, but portable, default implementation. | ||
217 | 2) Architecture-specific implementations that rewrite kernel .text at runtime. | ||
218 | |||
219 | If enabled, Feather-Trace will be based on 2) if available (currently only for x86). | ||
220 | However, if DEBUG_RODATA=y, then Feather-Trace will choose option 1) in any case | ||
221 | to avoid problems with write-protected .text pages. | ||
222 | |||
223 | Bottom line: to avoid increased overheads, choose DEBUG_RODATA=n. | ||
224 | |||
225 | Note that this option only enables the basic Feather-Trace infrastructure; | 214 | Note that this option only enables the basic Feather-Trace infrastructure; |
226 | you still need to enable SCHED_TASK_TRACE and/or SCHED_OVERHEAD_TRACE to | 215 | you still need to enable SCHED_TASK_TRACE and/or SCHED_OVERHEAD_TRACE to |
227 | actually enable any events. | 216 | actually enable any events. |