diff options
Diffstat (limited to 'litmus/Kconfig')
-rw-r--r-- | litmus/Kconfig | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/litmus/Kconfig b/litmus/Kconfig index 382b2e426437..70ddbaddc06f 100644 --- a/litmus/Kconfig +++ b/litmus/Kconfig | |||
@@ -1,3 +1,28 @@ | |||
1 | menu "LITMUS^RT" | 1 | menu "LITMUS^RT" |
2 | 2 | ||
3 | menu "Tracing" | ||
4 | |||
5 | config FEATHER_TRACE | ||
6 | bool "Feather-Trace Infrastructure" | ||
7 | default y | ||
8 | help | ||
9 | Feather-Trace basic tracing infrastructure. Includes device file | ||
10 | driver and instrumentation point support. | ||
11 | |||
12 | There are actually two implementations of Feather-Trace. | ||
13 | 1) A slower, but portable, default implementation. | ||
14 | 2) Architecture-specific implementations that rewrite kernel .text at runtime. | ||
15 | |||
16 | If enabled, Feather-Trace will be based on 2) if available (currently only for x86). | ||
17 | However, if DEBUG_RODATA=y, then Feather-Trace will choose option 1) in any case | ||
18 | to avoid problems with write-protected .text pages. | ||
19 | |||
20 | Bottom line: to avoid increased overheads, choose DEBUG_RODATA=n. | ||
21 | |||
22 | Note that this option only enables the basic Feather-Trace infrastructure; | ||
23 | you still need to enable SCHED_TASK_TRACE and/or SCHED_OVERHEAD_TRACE to | ||
24 | actually enable any events. | ||
25 | |||
26 | endmenu | ||
27 | |||
3 | endmenu | 28 | endmenu |