2012-04-20 21:45:54 +08:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
|
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
|
|
|
|
|
|
config FRAME_POINTER
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
2014-04-05 08:30:50 +08:00
|
|
|
config STRICT_DEVMEM
|
|
|
|
|
bool "Filter access to /dev/mem"
|
|
|
|
|
depends on MMU
|
|
|
|
|
help
|
|
|
|
|
If this option is disabled, you allow userspace (root) access to all
|
|
|
|
|
of memory, including kernel and userspace memory. Accidental
|
|
|
|
|
access to this is obviously disastrous, but specific access can
|
|
|
|
|
be used by people debugging the kernel.
|
|
|
|
|
|
|
|
|
|
If this option is switched on, the /dev/mem file only allows
|
|
|
|
|
userspace access to memory mapped peripherals.
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
2013-01-17 20:31:45 +08:00
|
|
|
config PID_IN_CONTEXTIDR
|
|
|
|
|
bool "Write the current PID to the CONTEXTIDR register"
|
|
|
|
|
help
|
|
|
|
|
Enabling this option causes the kernel to write the current PID to
|
|
|
|
|
the CONTEXTIDR register, at the expense of some additional
|
|
|
|
|
instructions during context switch. Say Y here only if you are
|
|
|
|
|
planning to use hardware trace tools with this kernel.
|
|
|
|
|
|
2012-04-20 21:45:54 +08:00
|
|
|
endmenu
|
