^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) # SPDX-License-Identifier: GPL-2.0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) config TRACE_IRQFLAGS_SUPPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) def_bool y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) config TRACE_IRQFLAGS_NMI_SUPPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) def_bool y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) config EARLY_PRINTK_USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) bool
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) config X86_VERBOSE_BOOTUP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) bool "Enable verbose x86 bootup info messages"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) Enables the informational output from the decompression stage
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) (e.g. bzImage) of the boot. If you disable this you will still
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) see errors. Disable this if you want silent bootup.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) config EARLY_PRINTK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) bool "Early printk" if EXPERT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24) Write kernel log output directly into the VGA buffer or to a serial
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) This is useful for kernel debugging when your machine crashes very
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) early before the console code is initialized. For normal operation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) it is not recommended because it looks ugly and doesn't cooperate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) with klogd/syslogd or the X server. You should normally say N here,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) unless you want to debug such a crash.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) config EARLY_PRINTK_DBGP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34) bool "Early printk via EHCI debug port"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) depends on EARLY_PRINTK && PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36) select EARLY_PRINTK_USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) Write kernel log output directly into the EHCI debug port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) This is useful for kernel debugging when your machine crashes very
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) early before the console code is initialized. For normal operation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) it is not recommended because it looks ugly and doesn't cooperate
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) with klogd/syslogd or the X server. You should normally say N here,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44) unless you want to debug such a crash. You need usb debug device.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) config EARLY_PRINTK_USB_XDBC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) bool "Early printk via the xHCI debug port"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48) depends on EARLY_PRINTK && PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) select EARLY_PRINTK_USB
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) Write kernel log output directly into the xHCI debug port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) One use for this feature is kernel debugging, for example when your
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) machine crashes very early before the regular console code is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) initialized. Other uses include simpler, lockless logging instead of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56) a full-blown printk console driver + klogd.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) For normal production environments this is normally not recommended,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) because it doesn't feed events into klogd/syslogd and doesn't try to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) print anything on the screen.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) You should normally say N here, unless you want to debug early
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) crashes or need a very simple printk logging facility.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) config COPY_MC_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66) def_bool n
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) config EFI_PGT_DUMP
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69) bool "Dump the EFI pagetable"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) depends on EFI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71) select PTDUMP_CORE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) Enable this if you want to dump the EFI page table before
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) enabling virtual mode. This can be used to debug miscellaneous
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75) issues with the mapping of the EFI runtime regions into that
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) table.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) config DEBUG_TLBFLUSH
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79) bool "Set upper limit of TLB entries to flush one-by-one"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) X86-only for now.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) This option allows the user to tune the amount of TLB entries the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) kernel flushes one-by-one instead of doing a full TLB flush. In
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) certain situations, the former is cheaper. This is controlled by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) tlb_flushall_shift knob under /sys/kernel/debug/x86. If you set it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89) to -1, the code flushes the whole TLB unconditionally. Otherwise,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) for positive values of it, the kernel will use single TLB entry
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91) invalidating instructions according to the following formula:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) flush_entries <= active_tlb_entries / 2^tlb_flushall_shift
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) If in doubt, say "N".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) config IOMMU_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) bool "Enable IOMMU debugging"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) depends on GART_IOMMU && DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100) depends on X86_64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) Force the IOMMU to on even when you have less than 4GB of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103) memory and add debugging code. On overflow always panic. And
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) allow to enable IOMMU leak tracing. Can be disabled at boot
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) time with iommu=noforce. This will also enable scatter gather
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) list merging. Currently not recommended for production
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) code. When you use it make sure you have a big enough
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108) IOMMU/AGP aperture. Most of the options enabled by this can
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) be set more finegrained using the iommu= command line
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) options. See Documentation/x86/x86_64/boot-options.rst for more
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111) details.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113) config IOMMU_LEAK
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) bool "IOMMU leak tracing"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) depends on IOMMU_DEBUG && DMA_API_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) Add a simple leak tracer to the IOMMU code. This is useful when you
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118) are debugging a buggy device driver that leaks IOMMU mappings.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120) config HAVE_MMIOTRACE_SUPPORT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) def_bool y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) config X86_DECODER_SELFTEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) bool "x86 instruction decoder selftest"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125) depends on DEBUG_KERNEL && INSTRUCTION_DECODER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) depends on !COMPILE_TEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) Perform x86 instruction decoder selftests at build time.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) This option is useful for checking the sanity of x86 instruction
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) decoder code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131) If unsure, say "N".
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133) choice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) prompt "IO delay type"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) default IO_DELAY_0X80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) config IO_DELAY_0X80
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) bool "port 0x80 based port-IO delay [recommended]"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) This is the traditional Linux IO delay used for in/out_p.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) It is the most tested hence safest selection here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) config IO_DELAY_0XED
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) bool "port 0xed based port-IO delay"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) Use port 0xed as the IO delay. This frees up port 0x80 which is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) often used as a hardware-debug port.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149) config IO_DELAY_UDELAY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) bool "udelay based port-IO delay"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) Use udelay(2) as the IO delay method. This provides the delay
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) while not having any side-effect on the IO port space.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) config IO_DELAY_NONE
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) bool "no port-IO delay"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) No port-IO delay. Will break on old boxes that require port-IO
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159) delay for certain operations. Should work on most new machines.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) endchoice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) config DEBUG_BOOT_PARAMS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) bool "Debug boot parameters"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165) depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) depends on DEBUG_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) This option will cause struct boot_params to be exported via debugfs.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) config CPA_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) bool "CPA self-test code"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174) Do change_page_attr() self-tests every 30 seconds.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) config DEBUG_ENTRY
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177) bool "Debug low-level entry code"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) This option enables sanity checks in x86's low-level entry code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) Some of these sanity checks may slow down kernel entries and
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) exits or otherwise impact performance.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) config DEBUG_NMI_SELFTEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) bool "NMI Selftest"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188) depends on DEBUG_KERNEL && X86_LOCAL_APIC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) Enabling this option turns on a quick NMI selftest to verify
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191) that the NMI behaves correctly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193) This might help diagnose strange hangs that rely on NMI to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) function properly.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) config DEBUG_IMR_SELFTEST
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) bool "Isolated Memory Region self test"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) depends on INTEL_IMR
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202) This option enables automated sanity testing of the IMR code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) Some simple tests are run to verify IMR bounds checking, alignment
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) and overlapping. This option is really only useful if you are
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205) debugging an IMR memory map or are modifying the IMR code and want to
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) test your changes.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208) If unsure say N here.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210) config X86_DEBUG_FPU
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) bool "Debug the x86 FPU code"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212) depends on DEBUG_KERNEL
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) default y
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) If this option is enabled then there will be extra sanity
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) checks and (boot time) debug printouts added to the kernel.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) This debugging adds some small amount of runtime overhead
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) to the kernel.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220) If unsure, say N.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) config PUNIT_ATOM_DEBUG
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 223) tristate "ATOM Punit debug driver"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 224) depends on PCI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 225) select DEBUG_FS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 226) select IOSF_MBI
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 227) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 228) This is a debug driver, which gets the power states
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 229) of all Punit North Complex devices. The power states of
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 230) each device is exposed as part of the debugfs interface.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 231) The current power state can be read from
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 232) /sys/kernel/debug/punit_atom/dev_power_state
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 233)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 234) choice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 235) prompt "Choose kernel unwinder"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 236) default UNWINDER_ORC if X86_64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 237) default UNWINDER_FRAME_POINTER if X86_32
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 238) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 239) This determines which method will be used for unwinding kernel stack
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 240) traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 241) livepatch, lockdep, and more.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 242)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 243) config UNWINDER_ORC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 244) bool "ORC unwinder"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 245) depends on X86_64
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 246) select STACK_VALIDATION
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 247) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 248) This option enables the ORC (Oops Rewind Capability) unwinder for
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 249) unwinding kernel stack traces. It uses a custom data format which is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 250) a simplified version of the DWARF Call Frame Information standard.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 251)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 252) This unwinder is more accurate across interrupt entry frames than the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 253) frame pointer unwinder. It also enables a 5-10% performance
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 254) improvement across the entire kernel compared to frame pointers.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 255)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 256) Enabling this option will increase the kernel's runtime memory usage
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 257) by roughly 2-4MB, depending on your kernel config.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 258)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 259) config UNWINDER_FRAME_POINTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 260) bool "Frame pointer unwinder"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 261) select FRAME_POINTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 262) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 263) This option enables the frame pointer unwinder for unwinding kernel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 264) stack traces.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 265)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 266) The unwinder itself is fast and it uses less RAM than the ORC
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 267) unwinder, but the kernel text size will grow by ~3% and the kernel's
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 268) overall performance will degrade by roughly 5-10%.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 269)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 270) config UNWINDER_GUESS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 271) bool "Guess unwinder"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 272) depends on EXPERT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 273) depends on !STACKDEPOT
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 274) help
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 275) This option enables the "guess" unwinder for unwinding kernel stack
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 276) traces. It scans the stack and reports every kernel text address it
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 277) finds. Some of the addresses it reports may be incorrect.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 278)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 279) While this option often produces false positives, it can still be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 280) useful in many cases. Unlike the other unwinders, it has no runtime
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 281) overhead.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 282)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 283) endchoice
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 284)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 285) config FRAME_POINTER
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 286) depends on !UNWINDER_ORC && !UNWINDER_GUESS
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 287) bool
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags