mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-25 13:43:55 +08:00
5ca43f6c3b
Most arches define CONFIG_DEBUG_STACK_USAGE exactly the same way. Move it to lib/Kconfig.debug so each arch doesn't have to define it. This obviously makes the option generic, but that's fine because the config is already used in generic code. It's not obvious to me that sysrq-P actually does anything caution by keeping the most inclusive wording. Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> Cc: Chris Metcalf <cmetcalf@tilera.com> Acked-by: David S. Miller <davem@davemloft.net> Acked-by: Richard Weinberger <richard@nod.at> Acked-by: Mike Frysinger <vapier@gentoo.org> Cc: Russell King <rmk@arm.linux.org.uk> Cc: Hirokazu Takata <takata@linux-m32r.org> Acked-by: Ralf Baechle <ralf@linux-mips.org> Cc: Paul Mackerras <paulus@samba.org> Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Chen Liqin <liqin.chen@sunplusct.com> Cc: Lennox Wu <lennox.wu@gmail.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: "H. Peter Anvin" <hpa@zytor.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
62 lines
1.9 KiB
Plaintext
62 lines
1.9 KiB
Plaintext
menu "Kernel hacking"
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
config STRICT_DEVMEM
|
|
bool "Filter access to /dev/mem"
|
|
depends on MMU
|
|
---help---
|
|
If this option is disabled, you allow userspace (root) access to all
|
|
of memory, including kernel and userspace memory. Accidental
|
|
access to this is obviously disastrous, but specific access can
|
|
be used by people debugging the kernel.
|
|
|
|
If this option is switched on, the /dev/mem file only allows
|
|
userspace access to memory mapped peripherals.
|
|
|
|
If in doubt, say Y.
|
|
|
|
config EARLY_PRINTK
|
|
def_bool DEBUG_OCD
|
|
help
|
|
Write kernel log output directly into the ocd or to a serial port.
|
|
|
|
This is useful for kernel debugging when your machine crashes very
|
|
early before the console code is initialized. For normal operation
|
|
it is not recommended because it looks ugly and doesn't cooperate
|
|
with klogd/syslogd or the X server. You should normally N here,
|
|
unless you want to debug such a crash.
|
|
|
|
# These options are only for real kernel hackers who want to get their hands dirty.
|
|
config DEBUG_LL
|
|
bool "Kernel low-level debugging functions"
|
|
depends on DEBUG_KERNEL
|
|
help
|
|
Say Y here to include definitions of printascii, printch, printhex
|
|
in the kernel. This is helpful if you are debugging code that
|
|
executes before the console is initialized.
|
|
|
|
config DEBUG_OCD
|
|
bool "Kernel low-level debugging via On-Chip-Debugger"
|
|
depends on DEBUG_LL
|
|
default y
|
|
help
|
|
Say Y here if you want the debug print routines to direct their
|
|
output to the UniCore On-Chip-Debugger channel using CP #1.
|
|
|
|
config DEBUG_OCD_BREAKPOINT
|
|
bool "Breakpoint support via On-Chip-Debugger"
|
|
depends on DEBUG_OCD
|
|
|
|
config DEBUG_UART
|
|
int "Kernel low-level debugging messages via serial port"
|
|
depends on DEBUG_LL
|
|
range 0 1
|
|
default "0"
|
|
help
|
|
Choice for UART for kernel low-level using PKUnity UARTS,
|
|
should be between zero and one. The port must have been
|
|
initialised by the boot-loader before use.
|
|
|
|
endmenu
|