Catalin Marinas | 8c2c3df | 2012-04-20 14:45:54 +0100 | [diff] [blame] | 1 | menu "Kernel hacking" |
| 2 | |
| 3 | source "lib/Kconfig.debug" |
| 4 | |
| 5 | config FRAME_POINTER |
| 6 | bool |
| 7 | default y |
| 8 | |
Laura Abbott | c9465b4 | 2014-11-26 00:28:39 +0000 | [diff] [blame] | 9 | config ARM64_PTDUMP |
| 10 | bool "Export kernel pagetable layout to userspace via debugfs" |
| 11 | depends on DEBUG_KERNEL |
| 12 | select DEBUG_FS |
| 13 | help |
| 14 | Say Y here if you want to show the kernel pagetable layout in a |
| 15 | debugfs file. This information is only useful for kernel developers |
| 16 | who are working in architecture specific areas of the kernel. |
| 17 | It is probably not a good idea to enable this feature in a production |
| 18 | kernel. |
| 19 | If in doubt, say "N" |
| 20 | |
Laura Abbott | d253b44 | 2014-04-05 01:30:50 +0100 | [diff] [blame] | 21 | config STRICT_DEVMEM |
| 22 | bool "Filter access to /dev/mem" |
| 23 | depends on MMU |
| 24 | help |
| 25 | If this option is disabled, you allow userspace (root) access to all |
| 26 | of memory, including kernel and userspace memory. Accidental |
| 27 | access to this is obviously disastrous, but specific access can |
| 28 | be used by people debugging the kernel. |
| 29 | |
| 30 | If this option is switched on, the /dev/mem file only allows |
| 31 | userspace access to memory mapped peripherals. |
| 32 | |
| 33 | If in doubt, say Y. |
| 34 | |
Will Deacon | ec45d1c | 2013-01-17 12:31:45 +0000 | [diff] [blame] | 35 | config PID_IN_CONTEXTIDR |
| 36 | bool "Write the current PID to the CONTEXTIDR register" |
| 37 | help |
| 38 | Enabling this option causes the kernel to write the current PID to |
| 39 | the CONTEXTIDR register, at the expense of some additional |
| 40 | instructions during context switch. Say Y here only if you are |
| 41 | planning to use hardware trace tools with this kernel. |
| 42 | |
Mark Rutland | da57a36 | 2014-06-24 16:51:37 +0100 | [diff] [blame] | 43 | config ARM64_RANDOMIZE_TEXT_OFFSET |
| 44 | bool "Randomize TEXT_OFFSET at build time" |
| 45 | help |
| 46 | Say Y here if you want the image load offset (AKA TEXT_OFFSET) |
| 47 | of the kernel to be randomized at build-time. When selected, |
| 48 | this option will cause TEXT_OFFSET to be randomized upon any |
| 49 | build of the kernel, and the offset will be reflected in the |
| 50 | text_offset field of the resulting Image. This can be used to |
| 51 | fuzz-test bootloaders which respect text_offset. |
| 52 | |
| 53 | This option is intended for bootloader and/or kernel testing |
| 54 | only. Bootloaders must make no assumptions regarding the value |
| 55 | of TEXT_OFFSET and platforms must not require a specific |
| 56 | value. |
| 57 | |
Laura Abbott | 11d91a7 | 2014-08-19 20:41:43 +0100 | [diff] [blame] | 58 | config DEBUG_SET_MODULE_RONX |
| 59 | bool "Set loadable kernel module data as NX and text as RO" |
| 60 | depends on MODULES |
| 61 | help |
| 62 | This option helps catch unintended modifications to loadable |
| 63 | kernel module's text and read-only data. It also prevents execution |
| 64 | of module data. Such protection may interfere with run-time code |
| 65 | patching and dynamic kernel tracing - and they might also protect |
| 66 | against certain classes of kernel exploits. |
| 67 | If in doubt, say "N". |
| 68 | |
Catalin Marinas | 8c2c3df | 2012-04-20 14:45:54 +0100 | [diff] [blame] | 69 | endmenu |