diff options
Diffstat (limited to 'kernel/trace/Kconfig')
| -rw-r--r-- | kernel/trace/Kconfig | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig index b416512ad17f..d006554888dc 100644 --- a/kernel/trace/Kconfig +++ b/kernel/trace/Kconfig | |||
| @@ -339,6 +339,27 @@ config POWER_TRACER | |||
| 339 | power management decisions, specifically the C-state and P-state | 339 | power management decisions, specifically the C-state and P-state |
| 340 | behavior. | 340 | behavior. |
| 341 | 341 | ||
| 342 | config KSYM_TRACER | ||
| 343 | bool "Trace read and write access on kernel memory locations" | ||
| 344 | depends on HAVE_HW_BREAKPOINT | ||
| 345 | select TRACING | ||
| 346 | help | ||
| 347 | This tracer helps find read and write operations on any given kernel | ||
| 348 | symbol i.e. /proc/kallsyms. | ||
| 349 | |||
| 350 | config PROFILE_KSYM_TRACER | ||
| 351 | bool "Profile all kernel memory accesses on 'watched' variables" | ||
| 352 | depends on KSYM_TRACER | ||
| 353 | help | ||
| 354 | This tracer profiles kernel accesses on variables watched through the | ||
| 355 | ksym tracer ftrace plugin. Depending upon the hardware, all read | ||
| 356 | and write operations on kernel variables can be monitored for | ||
| 357 | accesses. | ||
| 358 | |||
| 359 | The results will be displayed in: | ||
| 360 | /debugfs/tracing/profile_ksym | ||
| 361 | |||
| 362 | Say N if unsure. | ||
| 342 | 363 | ||
| 343 | config STACK_TRACER | 364 | config STACK_TRACER |
| 344 | bool "Trace max stack" | 365 | bool "Trace max stack" |
| @@ -428,6 +449,23 @@ config BLK_DEV_IO_TRACE | |||
| 428 | 449 | ||
| 429 | If unsure, say N. | 450 | If unsure, say N. |
| 430 | 451 | ||
| 452 | config KPROBE_EVENT | ||
| 453 | depends on KPROBES | ||
| 454 | depends on X86 | ||
| 455 | bool "Enable kprobes-based dynamic events" | ||
| 456 | select TRACING | ||
| 457 | default y | ||
| 458 | help | ||
| 459 | This allows the user to add tracing events (similar to tracepoints) on the fly | ||
| 460 | via the ftrace interface. See Documentation/trace/kprobetrace.txt | ||
| 461 | for more details. | ||
| 462 | |||
| 463 | Those events can be inserted wherever kprobes can probe, and record | ||
| 464 | various register and memory values. | ||
| 465 | |||
| 466 | This option is also required by perf-probe subcommand of perf tools. If | ||
| 467 | you want to use perf tools, this option is strongly recommended. | ||
| 468 | |||
| 431 | config DYNAMIC_FTRACE | 469 | config DYNAMIC_FTRACE |
| 432 | bool "enable/disable ftrace tracepoints dynamically" | 470 | bool "enable/disable ftrace tracepoints dynamically" |
| 433 | depends on FUNCTION_TRACER | 471 | depends on FUNCTION_TRACER |
