| 1 | menu "Kernel hacking" |
| 2 | |
| 3 | config TRACE_IRQFLAGS_SUPPORT |
| 4 | def_bool y |
| 5 | |
| 6 | source "lib/Kconfig.debug" |
| 7 | |
| 8 | config STRICT_DEVMEM |
| 9 | def_bool y |
| 10 | prompt "Filter access to /dev/mem" |
| 11 | ---help--- |
| 12 | This option restricts access to /dev/mem. If this option is |
| 13 | disabled, you allow userspace access to all memory, including |
| 14 | kernel and userspace memory. Accidental memory access is likely |
| 15 | to be disastrous. |
| 16 | Memory access is required for experts who want to debug the kernel. |
| 17 | |
| 18 | If you are unsure, say Y. |
| 19 | |
| 20 | config S390_PTDUMP |
| 21 | bool "Export kernel pagetable layout to userspace via debugfs" |
| 22 | depends on DEBUG_KERNEL |
| 23 | select DEBUG_FS |
| 24 | ---help--- |
| 25 | Say Y here if you want to show the kernel pagetable layout in a |
| 26 | debugfs file. This information is only useful for kernel developers |
| 27 | who are working in architecture specific areas of the kernel. |
| 28 | It is probably not a good idea to enable this feature in a production |
| 29 | kernel. |
| 30 | If in doubt, say "N" |
| 31 | |
| 32 | config DEBUG_SET_MODULE_RONX |
| 33 | def_bool y |
| 34 | depends on MODULES |
| 35 | endmenu |