2005-04-16 18:20:36 -04:00
|
|
|
|
|
|
|
config PRINTK_TIME
|
|
|
|
bool "Show timing information on printks"
|
|
|
|
help
|
|
|
|
Selecting this option causes timing information to be
|
|
|
|
included in printk output. This allows you to measure
|
|
|
|
the interval between kernel operations, including bootup
|
|
|
|
operations. This is useful for identifying long delays
|
|
|
|
in kernel startup.
|
|
|
|
|
|
|
|
|
|
|
|
config MAGIC_SYSRQ
|
|
|
|
bool "Magic SysRq key"
|
2006-01-09 23:54:51 -05:00
|
|
|
depends on !UML
|
2005-04-16 18:20:36 -04:00
|
|
|
help
|
|
|
|
If you say Y here, you will have some control over the system even
|
|
|
|
if the system crashes for example during kernel debugging (e.g., you
|
|
|
|
will be able to flush the buffer cache to disk, reboot the system
|
|
|
|
immediately or dump some status information). This is accomplished
|
|
|
|
by pressing various keys while holding SysRq (Alt+PrintScreen). It
|
|
|
|
also works on a serial console (on PC hardware at least), if you
|
|
|
|
send a BREAK and then within 5 seconds a command keypress. The
|
|
|
|
keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
|
|
|
|
unless you really know what this hack does.
|
|
|
|
|
2006-06-28 07:26:45 -04:00
|
|
|
config UNUSED_SYMBOLS
|
|
|
|
bool "Enable unused/obsolete exported symbols"
|
|
|
|
default y if X86
|
|
|
|
help
|
|
|
|
Unused but exported symbols make the kernel needlessly bigger. For
|
|
|
|
that reason most of these unused exports will soon be removed. This
|
|
|
|
option is provided temporarily to provide a transition period in case
|
|
|
|
some external kernel module needs one of these symbols anyway. If you
|
|
|
|
encounter such a case in your module, consider if you are actually
|
|
|
|
using the right API. (rationale: since nobody in the kernel is using
|
|
|
|
this in a module, there is a pretty good chance it's actually the
|
|
|
|
wrong interface to use). If you really need the symbol, please send a
|
|
|
|
mail to the linux kernel mailing list mentioning the symbol and why
|
|
|
|
you really need it, and what the merge plan to the mainline kernel for
|
|
|
|
your module is.
|
|
|
|
|
2006-01-09 23:54:51 -05:00
|
|
|
config DEBUG_KERNEL
|
|
|
|
bool "Kernel debugging"
|
|
|
|
help
|
|
|
|
Say Y here if you are developing drivers or trying to debug and
|
|
|
|
identify kernel problems.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config LOG_BUF_SHIFT
|
|
|
|
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
|
|
|
|
range 12 21
|
2006-01-06 03:19:28 -05:00
|
|
|
default 17 if S390
|
2005-04-16 18:20:36 -04:00
|
|
|
default 16 if X86_NUMAQ || IA64
|
|
|
|
default 15 if SMP
|
|
|
|
default 14
|
|
|
|
help
|
|
|
|
Select kernel log buffer size as a power of 2.
|
|
|
|
Defaults and Examples:
|
|
|
|
17 => 128 KB for S/390
|
|
|
|
16 => 64 KB for x86 NUMAQ or IA-64
|
|
|
|
15 => 32 KB for SMP
|
|
|
|
14 => 16 KB for uniprocessor
|
|
|
|
13 => 8 KB
|
|
|
|
12 => 4 KB
|
|
|
|
|
2005-09-06 18:16:27 -04:00
|
|
|
config DETECT_SOFTLOCKUP
|
|
|
|
bool "Detect Soft Lockups"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Say Y here to enable the kernel to detect "soft lockups",
|
|
|
|
which are bugs that cause the kernel to loop in kernel
|
|
|
|
mode for more than 10 seconds, without giving other tasks a
|
|
|
|
chance to run.
|
|
|
|
|
|
|
|
When a soft-lockup is detected, the kernel will print the
|
|
|
|
current stack trace (which you should report), but the
|
|
|
|
system will stay locked up. This feature has negligible
|
|
|
|
overhead.
|
|
|
|
|
|
|
|
(Note that "hard lockups" are separate type of bugs that
|
|
|
|
can be detected via the NMI-watchdog, on platforms that
|
|
|
|
support it.)
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config SCHEDSTATS
|
|
|
|
bool "Collect scheduler statistics"
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
|
|
|
help
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
scheduler and related routines to collect statistics about
|
|
|
|
scheduler behavior and provide them in /proc/schedstat. These
|
|
|
|
stats may be useful for both tuning and debugging the scheduler
|
|
|
|
If you aren't debugging the scheduler or trying to tune a specific
|
|
|
|
application, you can say N to avoid the very slight overhead
|
|
|
|
this adds.
|
|
|
|
|
|
|
|
config DEBUG_SLAB
|
2006-03-25 06:07:22 -05:00
|
|
|
bool "Debug slab memory allocations"
|
2006-01-08 04:01:42 -05:00
|
|
|
depends on DEBUG_KERNEL && SLAB
|
2005-04-16 18:20:36 -04:00
|
|
|
help
|
|
|
|
Say Y here to have the kernel do limited verification on memory
|
|
|
|
allocation as well as poisoning memory on free to catch use of freed
|
|
|
|
memory. This can make kmalloc/kfree-intensive workloads much slower.
|
|
|
|
|
2006-03-25 06:06:39 -05:00
|
|
|
config DEBUG_SLAB_LEAK
|
|
|
|
bool "Memory leak debugging"
|
|
|
|
depends on DEBUG_SLAB
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config DEBUG_PREEMPT
|
|
|
|
bool "Debug preemptible kernel"
|
2006-07-03 03:24:38 -04:00
|
|
|
depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
|
2005-04-16 18:20:36 -04:00
|
|
|
default y
|
|
|
|
help
|
|
|
|
If you say Y here then the kernel will use a debug variant of the
|
|
|
|
commonly used smp_processor_id() function and will print warnings
|
|
|
|
if kernel code uses it in a preemption-unsafe way. Also, the kernel
|
|
|
|
will detect preemption count underflows.
|
|
|
|
|
2006-06-27 05:54:55 -04:00
|
|
|
config DEBUG_RT_MUTEXES
|
|
|
|
bool "RT Mutex debugging, deadlock detection"
|
|
|
|
depends on DEBUG_KERNEL && RT_MUTEXES
|
|
|
|
help
|
|
|
|
This allows rt mutex semantics violations and rt mutex related
|
|
|
|
deadlocks (lockups) to be detected and reported automatically.
|
|
|
|
|
|
|
|
config DEBUG_PI_LIST
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
depends on DEBUG_RT_MUTEXES
|
|
|
|
|
2006-06-27 05:54:56 -04:00
|
|
|
config RT_MUTEX_TESTER
|
|
|
|
bool "Built-in scriptable tester for rt-mutexes"
|
2006-06-27 05:55:00 -04:00
|
|
|
depends on DEBUG_KERNEL && RT_MUTEXES
|
2006-06-27 05:54:56 -04:00
|
|
|
help
|
|
|
|
This option enables a rt-mutex tester.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config DEBUG_SPINLOCK
|
|
|
|
bool "Spinlock debugging"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Say Y here and build SMP to catch missing spinlock initialization
|
|
|
|
and certain other kinds of spinlock errors commonly made. This is
|
|
|
|
best used in conjunction with the NMI watchdog so that spinlock
|
|
|
|
deadlocks are also debuggable.
|
|
|
|
|
|
|
|
config DEBUG_SPINLOCK_SLEEP
|
|
|
|
bool "Sleep-inside-spinlock checking"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
If you say Y here, various routines which may sleep will become very
|
|
|
|
noisy if they are called with a spinlock held.
|
|
|
|
|
2006-07-03 03:24:48 -04:00
|
|
|
config DEBUG_LOCKING_API_SELFTESTS
|
|
|
|
bool "Locking API boot-time self-tests"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
Say Y here if you want the kernel to run a short self-test during
|
|
|
|
bootup. The self-test checks whether common types of locking bugs
|
|
|
|
are detected by debugging mechanisms or not. (if you disable
|
|
|
|
lock debugging then those bugs wont be detected of course.)
|
|
|
|
The following locking APIs are covered: spinlocks, rwlocks,
|
|
|
|
mutexes and rwsems.
|
|
|
|
|
2006-07-03 03:24:38 -04:00
|
|
|
config STACKTRACE
|
|
|
|
bool
|
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config DEBUG_KOBJECT
|
|
|
|
bool "kobject debugging"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
If you say Y here, some extra kobject debugging messages will be sent
|
|
|
|
to the syslog.
|
|
|
|
|
|
|
|
config DEBUG_HIGHMEM
|
|
|
|
bool "Highmem debugging"
|
|
|
|
depends on DEBUG_KERNEL && HIGHMEM
|
|
|
|
help
|
|
|
|
This options enables addition error checking for high memory systems.
|
|
|
|
Disable for production systems.
|
|
|
|
|
|
|
|
config DEBUG_BUGVERBOSE
|
|
|
|
bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
|
2005-05-01 11:59:01 -04:00
|
|
|
depends on BUG
|
2005-10-30 17:59:20 -05:00
|
|
|
depends on ARM || ARM26 || M32R || M68K || SPARC32 || SPARC64 || X86_32 || FRV
|
2005-04-16 18:20:36 -04:00
|
|
|
default !EMBEDDED
|
|
|
|
help
|
|
|
|
Say Y here to make BUG() panics output the file name and line number
|
|
|
|
of the BUG call as well as the EIP and oops trace. This aids
|
|
|
|
debugging but costs about 70-100K of memory.
|
|
|
|
|
|
|
|
config DEBUG_INFO
|
|
|
|
bool "Compile the kernel with debug info"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
|
|
|
If you say Y here the resulting kernel image will include
|
|
|
|
debugging info resulting in a larger kernel image.
|
|
|
|
Say Y here only if you plan to debug the kernel.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
config DEBUG_FS
|
|
|
|
bool "Debug Filesystem"
|
2006-03-26 07:38:54 -05:00
|
|
|
depends on SYSFS
|
2005-04-16 18:20:36 -04:00
|
|
|
help
|
|
|
|
debugfs is a virtual file system that kernel developers use to put
|
|
|
|
debugging files into. Enable this option to be able to read and
|
|
|
|
write to these files.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2005-10-30 18:03:12 -05:00
|
|
|
config DEBUG_VM
|
|
|
|
bool "Debug VM"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
help
|
2006-01-06 03:10:58 -05:00
|
|
|
Enable this to turn on extended checks in the virtual-memory system
|
|
|
|
that may impact performance.
|
2005-10-30 18:03:12 -05:00
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
2005-04-16 18:20:36 -04:00
|
|
|
config FRAME_POINTER
|
|
|
|
bool "Compile the kernel with frame pointers"
|
2006-07-03 03:24:38 -04:00
|
|
|
depends on DEBUG_KERNEL && (X86 || CRIS || M68K || M68KNOMMU || FRV || UML || S390)
|
2005-05-28 18:51:59 -04:00
|
|
|
default y if DEBUG_INFO && UML
|
2005-04-16 18:20:36 -04:00
|
|
|
help
|
|
|
|
If you say Y here the resulting kernel image will be slightly larger
|
2005-10-30 18:02:51 -05:00
|
|
|
and slower, but it might give very useful debugging information on
|
|
|
|
some architectures or if you use external debuggers.
|
2005-09-12 12:49:25 -04:00
|
|
|
If you don't debug the kernel, you can say N.
|
2005-04-16 18:20:36 -04:00
|
|
|
|
2006-03-24 06:16:19 -05:00
|
|
|
config UNWIND_INFO
|
|
|
|
bool "Compile the kernel with frame unwind information"
|
2006-06-26 07:57:28 -04:00
|
|
|
depends on !IA64 && !PARISC
|
|
|
|
depends on !MODULES || !(MIPS || PPC || SUPERH || V850)
|
2006-03-24 06:16:19 -05:00
|
|
|
help
|
|
|
|
If you say Y here the resulting kernel image will be slightly larger
|
|
|
|
but not slower, and it will give very useful debugging information.
|
|
|
|
If you don't debug the kernel, you can say N, but we may not be able
|
|
|
|
to solve problems without frame unwind information or frame pointers.
|
|
|
|
|
2006-06-26 07:57:28 -04:00
|
|
|
config STACK_UNWIND
|
|
|
|
bool "Stack unwind support"
|
|
|
|
depends on UNWIND_INFO
|
2006-06-26 07:57:41 -04:00
|
|
|
depends on X86
|
2006-06-26 07:57:28 -04:00
|
|
|
help
|
|
|
|
This enables more precise stack traces, omitting all unrelated
|
|
|
|
occurrences of pointers into kernel code from the dump.
|
|
|
|
|
2006-01-14 16:21:33 -05:00
|
|
|
config FORCED_INLINING
|
|
|
|
bool "Force gcc to inline functions marked 'inline'"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
This option determines if the kernel forces gcc to inline the functions
|
|
|
|
developers have marked 'inline'. Doing so takes away freedom from gcc to
|
|
|
|
do what it thinks is best, which is desirable for the gcc 3.x series of
|
|
|
|
compilers. The gcc 4.x series have a rewritten inlining algorithm and
|
|
|
|
disabling this option will generate a smaller kernel there. Hopefully
|
|
|
|
this algorithm is so good that allowing gcc4 to make the decision can
|
|
|
|
become the default in the future, until then this option is there to
|
|
|
|
test gcc for this.
|
|
|
|
|
2005-10-30 18:03:12 -05:00
|
|
|
config RCU_TORTURE_TEST
|
|
|
|
tristate "torture tests for RCU"
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
This option provides a kernel module that runs torture tests
|
|
|
|
on the RCU infrastructure. The kernel module may be built
|
|
|
|
after the fact on the running kernel to be tested, if desired.
|
|
|
|
|
|
|
|
Say Y here if you want RCU torture tests to start automatically
|
|
|
|
at boot time (you probably don't).
|
|
|
|
Say M if you want the RCU torture tests to build as a module.
|
|
|
|
Say N if you are unsure.
|