3 source "lib/Kconfig.debug"
10 bool "Export kernel pagetable layout to userspace via debugfs"
11 depends on DEBUG_KERNEL
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
22 bool "Filter access to /dev/mem"
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.
30 If this option is switched on, the /dev/mem file only allows
31 userspace access to memory mapped peripherals.
35 config PID_IN_CONTEXTIDR
36 bool "Write the current PID to the CONTEXTIDR register"
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.
43 config ARM64_RANDOMIZE_TEXT_OFFSET
44 bool "Randomize TEXT_OFFSET at build time"
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.
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
58 config DEBUG_SET_MODULE_RONX
59 bool "Set loadable kernel module data as NX and text as RO"
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.