menu "Kernel hacking"source "lib/Kconfig.debug"config DEBUG_RWLOCK bool "Read-write spinlock debugging" depends on DEBUG_KERNEL && SMP help If you say Y here then read-write lock processing will count how many times it has tried to get the lock and issue an error message after too many attempts. If you suspect a rwlock problem or a kernel hacker asks for this option then say Y. Otherwise say N.config DEBUG_RODATA bool "Write protect kernel read-only data structures" depends on DEBUG_KERNEL help Mark the kernel read-only data as write-protected in the pagetables, in order to catch accidental (and incorrect) writes to such const data. This option may have a slight performance impact because a portion of the kernel code won't be covered by a TLB anymore. If in doubt, say "N".endmenu
menu "Kernel hacking"
source "lib/Kconfig.debug"
config DEBUG_RWLOCK
bool "Read-write spinlock debugging"
depends on DEBUG_KERNEL && SMP
help
If you say Y here then read-write lock processing will count how many
times it has tried to get the lock and issue an error message after
too many attempts. If you suspect a rwlock problem or a kernel
hacker asks for this option then say Y. Otherwise say N.
config DEBUG_RODATA
bool "Write protect kernel read-only data structures"
depends on DEBUG_KERNEL
help
Mark the kernel read-only data as write-protected in the pagetables,
in order to catch accidental (and incorrect) writes to such const
data. This option may have a slight performance impact because a
portion of the kernel code won't be covered by a TLB anymore.
If in doubt, say "N".
endmenu