mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 04:34:11 +08:00
1da177e4c3
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
75 lines
2.0 KiB
Plaintext
75 lines
2.0 KiB
Plaintext
menu "Kernel hacking"
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
config EARLY_PRINTK
|
|
bool "Early printk"
|
|
depends on EMBEDDED && DEBUG_KERNEL
|
|
default n
|
|
help
|
|
Write kernel log output directly into the VGA buffer 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.
|
|
|
|
config DEBUG_STACKOVERFLOW
|
|
bool "Check for stack overflows"
|
|
depends on DEBUG_KERNEL
|
|
|
|
config DEBUG_PAGEALLOC
|
|
bool "Page alloc debugging"
|
|
depends on DEBUG_KERNEL
|
|
help
|
|
Unmap pages from the kernel linear mapping after free_pages().
|
|
This results in a large slowdown, but helps to find certain types
|
|
of memory corruptions.
|
|
|
|
config GDBSTUB
|
|
bool "Remote GDB kernel debugging"
|
|
depends on DEBUG_KERNEL
|
|
select DEBUG_INFO
|
|
select FRAME_POINTER
|
|
help
|
|
If you say Y here, it will be possible to remotely debug the kernel
|
|
using gdb. This enlarges your kernel ELF image disk size by several
|
|
megabytes and requires a machine with more than 16 MB, better 32 MB
|
|
RAM to avoid excessive linking time. This is only useful for kernel
|
|
hackers. If unsure, say N.
|
|
|
|
choice
|
|
prompt "GDB stub port"
|
|
default GDBSTUB_UART1
|
|
depends on GDBSTUB
|
|
help
|
|
Select the on-CPU port used for GDB-stub
|
|
|
|
config GDBSTUB_UART0
|
|
bool "/dev/ttyS0"
|
|
|
|
config GDBSTUB_UART1
|
|
bool "/dev/ttyS1"
|
|
|
|
endchoice
|
|
|
|
config GDBSTUB_IMMEDIATE
|
|
bool "Break into GDB stub immediately"
|
|
depends on GDBSTUB
|
|
help
|
|
If you say Y here, GDB stub will break into the program as soon as
|
|
possible, leaving the program counter at the beginning of
|
|
start_kernel() in init/main.c.
|
|
|
|
config GDB_CONSOLE
|
|
bool "Console output to GDB"
|
|
depends on GDBSTUB
|
|
help
|
|
If you are using GDB for remote debugging over a serial port and
|
|
would like kernel messages to be formatted into GDB $O packets so
|
|
that GDB prints them as program output, say 'Y'.
|
|
|
|
endmenu
|