1# SPDX-License-Identifier: GPL-2.0-only 2 3config ARM64_PTDUMP_CORE 4 def_bool n 5 6config ARM64_PTDUMP_DEBUGFS 7 bool "Export kernel pagetable layout to userspace via debugfs" 8 depends on DEBUG_KERNEL 9 select ARM64_PTDUMP_CORE 10 select DEBUG_FS 11 help 12 Say Y here if you want to show the kernel pagetable layout in a 13 debugfs file. This information is only useful for kernel developers 14 who are working in architecture specific areas of the kernel. 15 It is probably not a good idea to enable this feature in a production 16 kernel. 17 18 If in doubt, say N. 19 20config PID_IN_CONTEXTIDR 21 bool "Write the current PID to the CONTEXTIDR register" 22 help 23 Enabling this option causes the kernel to write the current PID to 24 the CONTEXTIDR register, at the expense of some additional 25 instructions during context switch. Say Y here only if you are 26 planning to use hardware trace tools with this kernel. 27 28config ARM64_RANDOMIZE_TEXT_OFFSET 29 bool "Randomize TEXT_OFFSET at build time" 30 help 31 Say Y here if you want the image load offset (AKA TEXT_OFFSET) 32 of the kernel to be randomized at build-time. When selected, 33 this option will cause TEXT_OFFSET to be randomized upon any 34 build of the kernel, and the offset will be reflected in the 35 text_offset field of the resulting Image. This can be used to 36 fuzz-test bootloaders which respect text_offset. 37 38 This option is intended for bootloader and/or kernel testing 39 only. Bootloaders must make no assumptions regarding the value 40 of TEXT_OFFSET and platforms must not require a specific 41 value. 42 43config DEBUG_WX 44 bool "Warn on W+X mappings at boot" 45 select ARM64_PTDUMP_CORE 46 ---help--- 47 Generate a warning if any W+X mappings are found at boot. 48 49 This is useful for discovering cases where the kernel is leaving 50 W+X mappings after applying NX, as such mappings are a security risk. 51 This check also includes UXN, which should be set on all kernel 52 mappings. 53 54 Look for a message in dmesg output like this: 55 56 arm64/mm: Checked W+X mappings: passed, no W+X pages found. 57 58 or like this, if the check failed: 59 60 arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found. 61 62 Note that even if the check fails, your kernel is possibly 63 still fine, as W+X mappings are not a security hole in 64 themselves, what they do is that they make the exploitation 65 of other unfixed kernel bugs easier. 66 67 There is no runtime or memory usage effect of this option 68 once the kernel has booted up - it's a one time check. 69 70 If in doubt, say "Y". 71 72config DEBUG_ALIGN_RODATA 73 depends on STRICT_KERNEL_RWX 74 bool "Align linker sections up to SECTION_SIZE" 75 help 76 If this option is enabled, sections that may potentially be marked as 77 read only or non-executable will be aligned up to the section size of 78 the kernel. This prevents sections from being split into pages and 79 avoids a potential TLB penalty. The downside is an increase in 80 alignment and potentially wasted space. Turn on this option if 81 performance is more important than memory pressure. 82 83 If in doubt, say N. 84 85config DEBUG_EFI 86 depends on EFI && DEBUG_INFO 87 bool "UEFI debugging" 88 help 89 Enable this option to include EFI specific debugging features into 90 the kernel that are only useful when using a debug build of the 91 UEFI firmware 92 93config ARM64_RELOC_TEST 94 depends on m 95 tristate "Relocation testing module" 96 97source "drivers/hwtracing/coresight/Kconfig" 98