ARM kprobes: let's enable it
Signed-off-by: Nicolas Pitre <nico@marvell.com>
This commit is contained in:
parent
796969104c
commit
5de865b4c5
@ -141,6 +141,7 @@ architectures:
|
|||||||
- ppc64
|
- ppc64
|
||||||
- ia64 (Does not support probes on instruction slot1.)
|
- ia64 (Does not support probes on instruction slot1.)
|
||||||
- sparc64 (Return probes not yet implemented.)
|
- sparc64 (Return probes not yet implemented.)
|
||||||
|
- arm
|
||||||
|
|
||||||
3. Configuring Kprobes
|
3. Configuring Kprobes
|
||||||
|
|
||||||
|
@ -43,6 +43,16 @@ config OPROFILE_MPCORE
|
|||||||
config OPROFILE_ARM11_CORE
|
config OPROFILE_ARM11_CORE
|
||||||
bool
|
bool
|
||||||
|
|
||||||
|
config KPROBES
|
||||||
|
bool "Kprobes"
|
||||||
|
depends on KALLSYMS && MODULES && !UML && !XIP_KERNEL
|
||||||
|
help
|
||||||
|
Kprobes allows you to trap at almost any kernel address and
|
||||||
|
execute a callback function. register_kprobe() establishes
|
||||||
|
a probepoint and specifies the callback. Kprobes is useful
|
||||||
|
for kernel debugging, non-intrusive instrumentation and testing.
|
||||||
|
If in doubt, say "N".
|
||||||
|
|
||||||
config MARKERS
|
config MARKERS
|
||||||
bool "Activate markers"
|
bool "Activate markers"
|
||||||
help
|
help
|
||||||
|
Loading…
x
Reference in New Issue
Block a user