2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config PRINTK_TIME
|
|
|
|
|
bool "Show timing information on printks"
|
2006-12-07 12:36:38 +08:00
|
|
|
depends on PRINTK
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
|
2006-08-15 13:43:18 +08:00
|
|
|
config ENABLE_MUST_CHECK
|
|
|
|
|
bool "Enable __must_check logic"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable the __must_check logic in the kernel build. Disable this to
|
|
|
|
|
suppress the "warning: ignoring return value of 'foo', declared with
|
|
|
|
|
attribute warn_unused_result" messages.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config MAGIC_SYSRQ
|
|
|
|
|
bool "Magic SysRq key"
|
2006-01-10 12:54:51 +08:00
|
|
|
depends on !UML
|
2005-04-17 06:20:36 +08: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 19:26:45 +08: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-12-10 18:18:37 +08:00
|
|
|
config DEBUG_FS
|
|
|
|
|
bool "Debug Filesystem"
|
|
|
|
|
depends on SYSFS
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
config HEADERS_CHECK
|
|
|
|
|
bool "Run 'make headers_check' when building vmlinux"
|
|
|
|
|
depends on !UML
|
|
|
|
|
help
|
|
|
|
|
This option will extract the user-visible kernel headers whenever
|
|
|
|
|
building the kernel, and will run basic sanity checks on them to
|
|
|
|
|
ensure that exported files do not attempt to include files which
|
|
|
|
|
were not exported, etc.
|
|
|
|
|
|
|
|
|
|
If you're making modifications to header files which are
|
|
|
|
|
relevant for userspace, say 'Y', and check the headers
|
|
|
|
|
exported to $(INSTALL_HDR_PATH) (usually 'usr/include' in
|
|
|
|
|
your build tree), to make sure they're suitable.
|
|
|
|
|
|
2006-01-10 12:54:51 +08:00
|
|
|
config DEBUG_KERNEL
|
|
|
|
|
bool "Kernel debugging"
|
|
|
|
|
help
|
|
|
|
|
Say Y here if you are developing drivers or trying to debug and
|
|
|
|
|
identify kernel problems.
|
|
|
|
|
|
2007-02-12 16:52:00 +08:00
|
|
|
config DEBUG_SHIRQ
|
|
|
|
|
bool "Debug shared IRQ handlers"
|
|
|
|
|
depends on DEBUG_KERNEL && GENERIC_HARDIRQS
|
|
|
|
|
help
|
|
|
|
|
Enable this to generate a spurious interrupt as soon as a shared
|
|
|
|
|
interrupt handler is registered, and just before one is deregistered.
|
|
|
|
|
Drivers ought to be able to handle interrupts coming in at those
|
|
|
|
|
points; some don't and need to be caught.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config LOG_BUF_SHIFT
|
|
|
|
|
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
|
|
|
|
|
range 12 21
|
[PATCH] lockdep: core
Do 'make oldconfig' and accept all the defaults for new config options -
reboot into the kernel and if everything goes well it should boot up fine and
you should have /proc/lockdep and /proc/lockdep_stats files.
Typically if the lock validator finds some problem it will print out
voluminous debug output that begins with "BUG: ..." and which syslog output
can be used by kernel developers to figure out the precise locking scenario.
What does the lock validator do? It "observes" and maps all locking rules as
they occur dynamically (as triggered by the kernel's natural use of spinlocks,
rwlocks, mutexes and rwsems). Whenever the lock validator subsystem detects a
new locking scenario, it validates this new rule against the existing set of
rules. If this new rule is consistent with the existing set of rules then the
new rule is added transparently and the kernel continues as normal. If the
new rule could create a deadlock scenario then this condition is printed out.
When determining validity of locking, all possible "deadlock scenarios" are
considered: assuming arbitrary number of CPUs, arbitrary irq context and task
context constellations, running arbitrary combinations of all the existing
locking scenarios. In a typical system this means millions of separate
scenarios. This is why we call it a "locking correctness" validator - for all
rules that are observed the lock validator proves it with mathematical
certainty that a deadlock could not occur (assuming that the lock validator
implementation itself is correct and its internal data structures are not
corrupted by some other kernel subsystem). [see more details and conditionals
of this statement in include/linux/lockdep.h and
Documentation/lockdep-design.txt]
Furthermore, this "all possible scenarios" property of the validator also
enables the finding of complex, highly unlikely multi-CPU multi-context races
via single single-context rules, increasing the likelyhood of finding bugs
drastically. In practical terms: the lock validator already found a bug in
the upstream kernel that could only occur on systems with 3 or more CPUs, and
which needed 3 very unlikely code sequences to occur at once on the 3 CPUs.
That bug was found and reported on a single-CPU system (!). So in essence a
race will be found "piecemail-wise", triggering all the necessary components
for the race, without having to reproduce the race scenario itself! In its
short existence the lock validator found and reported many bugs before they
actually caused a real deadlock.
To further increase the efficiency of the validator, the mapping is not per
"lock instance", but per "lock-class". For example, all struct inode objects
in the kernel have inode->inotify_mutex. If there are 10,000 inodes cached,
then there are 10,000 lock objects. But ->inotify_mutex is a single "lock
type", and all locking activities that occur against ->inotify_mutex are
"unified" into this single lock-class. The advantage of the lock-class
approach is that all historical ->inotify_mutex uses are mapped into a single
(and as narrow as possible) set of locking rules - regardless of how many
different tasks or inode structures it took to build this set of rules. The
set of rules persist during the lifetime of the kernel.
To see the rough magnitude of checking that the lock validator does, here's a
portion of /proc/lockdep_stats, fresh after bootup:
lock-classes: 694 [max: 2048]
direct dependencies: 1598 [max: 8192]
indirect dependencies: 17896
all direct dependencies: 16206
dependency chains: 1910 [max: 8192]
in-hardirq chains: 17
in-softirq chains: 105
in-process chains: 1065
stack-trace entries: 38761 [max: 131072]
combined max dependencies: 2033928
hardirq-safe locks: 24
hardirq-unsafe locks: 176
softirq-safe locks: 53
softirq-unsafe locks: 137
irq-safe locks: 59
irq-unsafe locks: 176
The lock validator has observed 1598 actual single-thread locking patterns,
and has validated all possible 2033928 distinct locking scenarios.
More details about the design of the lock validator can be found in
Documentation/lockdep-design.txt, which can also found at:
http://redhat.com/~mingo/lockdep-patches/lockdep-design.txt
[bunk@stusta.de: cleanups]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-07-03 15:24:50 +08:00
|
|
|
default 17 if S390 || LOCKDEP
|
2005-04-17 06:20:36 +08: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-07 06:16:27 +08:00
|
|
|
config DETECT_SOFTLOCKUP
|
|
|
|
|
bool "Detect Soft Lockups"
|
2006-10-11 16:20:44 +08:00
|
|
|
depends on DEBUG_KERNEL && !S390
|
2005-09-07 06:16:27 +08:00
|
|
|
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-17 06:20:36 +08: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.
|
|
|
|
|
|
[PATCH] Add debugging feature /proc/timer_stat
Add /proc/timer_stats support: debugging feature to profile timer expiration.
Both the starting site, process/PID and the expiration function is captured.
This allows the quick identification of timer event sources in a system.
Sample output:
# echo 1 > /proc/timer_stats
# cat /proc/timer_stats
Timer Stats Version: v0.1
Sample period: 4.010 s
24, 0 swapper hrtimer_stop_sched_tick (hrtimer_sched_tick)
11, 0 swapper sk_reset_timer (tcp_delack_timer)
6, 0 swapper hrtimer_stop_sched_tick (hrtimer_sched_tick)
2, 1 swapper queue_delayed_work_on (delayed_work_timer_fn)
17, 0 swapper hrtimer_restart_sched_tick (hrtimer_sched_tick)
2, 1 swapper queue_delayed_work_on (delayed_work_timer_fn)
4, 2050 pcscd do_nanosleep (hrtimer_wakeup)
5, 4179 sshd sk_reset_timer (tcp_write_timer)
4, 2248 yum-updatesd schedule_timeout (process_timeout)
18, 0 swapper hrtimer_restart_sched_tick (hrtimer_sched_tick)
3, 0 swapper sk_reset_timer (tcp_delack_timer)
1, 1 swapper neigh_table_init_no_netlink (neigh_periodic_timer)
2, 1 swapper e1000_up (e1000_watchdog)
1, 1 init schedule_timeout (process_timeout)
100 total events, 25.24 events/sec
[ cleanups and hrtimers support from Thomas Gleixner <tglx@linutronix.de> ]
[bunk@stusta.de: nr_entries can become static]
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: john stultz <johnstul@us.ibm.com>
Cc: Roman Zippel <zippel@linux-m68k.org>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-02-16 17:28:13 +08:00
|
|
|
config TIMER_STATS
|
|
|
|
|
bool "Collect kernel timers statistics"
|
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
|
timer routines to collect statistics about kernel timers being
|
|
|
|
|
reprogrammed. The statistics can be read from /proc/timer_stats.
|
|
|
|
|
The statistics collection is started by writing 1 to /proc/timer_stats,
|
|
|
|
|
writing 0 stops it. This feature is useful to collect information
|
|
|
|
|
about timer usage patterns in kernel and userspace.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_SLAB
|
2006-03-25 19:07:22 +08:00
|
|
|
bool "Debug slab memory allocations"
|
2006-01-08 17:01:42 +08:00
|
|
|
depends on DEBUG_KERNEL && SLAB
|
2005-04-17 06:20:36 +08: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 19:06:39 +08:00
|
|
|
config DEBUG_SLAB_LEAK
|
|
|
|
|
bool "Memory leak debugging"
|
|
|
|
|
depends on DEBUG_SLAB
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_PREEMPT
|
|
|
|
|
bool "Debug preemptible kernel"
|
2006-07-03 15:24:38 +08:00
|
|
|
depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
|
2005-04-17 06:20:36 +08: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 17:54:55 +08: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 17:54:56 +08:00
|
|
|
config RT_MUTEX_TESTER
|
|
|
|
|
bool "Built-in scriptable tester for rt-mutexes"
|
2006-06-27 17:55:00 +08:00
|
|
|
depends on DEBUG_KERNEL && RT_MUTEXES
|
2006-06-27 17:54:56 +08:00
|
|
|
help
|
|
|
|
|
This option enables a rt-mutex tester.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_SPINLOCK
|
2006-07-03 15:24:55 +08:00
|
|
|
bool "Spinlock and rw-lock debugging: basic checks"
|
2005-04-17 06:20:36 +08:00
|
|
|
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.
|
|
|
|
|
|
2006-07-03 15:24:55 +08:00
|
|
|
config DEBUG_MUTEXES
|
|
|
|
|
bool "Mutex debugging: basic checks"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
This feature allows mutex semantics violations to be detected and
|
|
|
|
|
reported.
|
|
|
|
|
|
|
|
|
|
config DEBUG_LOCK_ALLOC
|
|
|
|
|
bool "Lock debugging: detect incorrect freeing of live locks"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
|
select LOCKDEP
|
|
|
|
|
help
|
|
|
|
|
This feature will check whether any held lock (spinlock, rwlock,
|
|
|
|
|
mutex or rwsem) is incorrectly freed by the kernel, via any of the
|
|
|
|
|
memory-freeing routines (kfree(), kmem_cache_free(), free_pages(),
|
|
|
|
|
vfree(), etc.), whether a live lock is incorrectly reinitialized via
|
|
|
|
|
spin_lock_init()/mutex_init()/etc., or whether there is any lock
|
|
|
|
|
held during task exit.
|
|
|
|
|
|
|
|
|
|
config PROVE_LOCKING
|
|
|
|
|
bool "Lock debugging: prove locking correctness"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select LOCKDEP
|
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
|
select DEBUG_LOCK_ALLOC
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This feature enables the kernel to prove that all locking
|
|
|
|
|
that occurs in the kernel runtime is mathematically
|
|
|
|
|
correct: that under no circumstance could an arbitrary (and
|
|
|
|
|
not yet triggered) combination of observed locking
|
|
|
|
|
sequences (on an arbitrary number of CPUs, running an
|
|
|
|
|
arbitrary number of tasks and interrupt contexts) cause a
|
|
|
|
|
deadlock.
|
|
|
|
|
|
|
|
|
|
In short, this feature enables the kernel to report locking
|
|
|
|
|
related deadlocks before they actually occur.
|
|
|
|
|
|
|
|
|
|
The proof does not depend on how hard and complex a
|
|
|
|
|
deadlock scenario would be to trigger: how many
|
|
|
|
|
participant CPUs, tasks and irq-contexts would be needed
|
|
|
|
|
for it to trigger. The proof also does not depend on
|
|
|
|
|
timing: if a race and a resulting deadlock is possible
|
|
|
|
|
theoretically (no matter how unlikely the race scenario
|
|
|
|
|
is), it will be proven so and will immediately be
|
|
|
|
|
reported by the kernel (once the event is observed that
|
|
|
|
|
makes the deadlock theoretically possible).
|
|
|
|
|
|
|
|
|
|
If a deadlock is impossible (i.e. the locking rules, as
|
|
|
|
|
observed by the kernel, are mathematically correct), the
|
|
|
|
|
kernel reports nothing.
|
|
|
|
|
|
|
|
|
|
NOTE: this feature can also be enabled for rwlocks, mutexes
|
|
|
|
|
and rwsems - in which case all dependencies between these
|
|
|
|
|
different locking variants are observed and mapped too, and
|
|
|
|
|
the proof of observed correctness is also maintained for an
|
|
|
|
|
arbitrary combination of these separate locking variants.
|
|
|
|
|
|
|
|
|
|
For more details, see Documentation/lockdep-design.txt.
|
|
|
|
|
|
|
|
|
|
config LOCKDEP
|
|
|
|
|
bool
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 15:24:55 +08:00
|
|
|
select STACKTRACE
|
2007-04-26 15:20:15 +08:00
|
|
|
select FRAME_POINTER if !X86 && !MIPS
|
2006-07-03 15:24:55 +08:00
|
|
|
select KALLSYMS
|
|
|
|
|
select KALLSYMS_ALL
|
|
|
|
|
|
|
|
|
|
config DEBUG_LOCKDEP
|
|
|
|
|
bool "Lock dependency engine debugging"
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL && LOCKDEP
|
2006-07-03 15:24:55 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here, the lock dependency engine will do
|
|
|
|
|
additional runtime checks to debug itself, at the price
|
|
|
|
|
of more runtime overhead.
|
|
|
|
|
|
|
|
|
|
config TRACE_IRQFLAGS
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2006-07-03 15:24:55 +08:00
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
depends on TRACE_IRQFLAGS_SUPPORT
|
|
|
|
|
depends on PROVE_LOCKING
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config DEBUG_SPINLOCK_SLEEP
|
2006-07-03 15:24:55 +08:00
|
|
|
bool "Spinlock debugging: sleep-inside-spinlock checking"
|
2005-04-17 06:20:36 +08:00
|
|
|
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 15:24:48 +08: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 15:24:38 +08:00
|
|
|
config STACKTRACE
|
|
|
|
|
bool
|
2006-07-14 15:24:32 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2006-07-03 15:24:38 +08:00
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
|
|
2005-04-17 06:20:36 +08: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 23:59:01 +08:00
|
|
|
depends on BUG
|
blackfin architecture
This adds support for the Analog Devices Blackfin processor architecture, and
currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561
(Dual Core) devices, with a variety of development platforms including those
avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP,
BF561-EZKIT), and Bluetechnix! Tinyboards.
The Blackfin architecture was jointly developed by Intel and Analog Devices
Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in
December of 2000. Since then ADI has put this core into its Blackfin
processor family of devices. The Blackfin core has the advantages of a clean,
orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC
(Multiply/Accumulate), state-of-the-art signal processing engine and
single-instruction, multiple-data (SIMD) multimedia capabilities into a single
instruction-set architecture.
The Blackfin architecture, including the instruction set, is described by the
ADSP-BF53x/BF56x Blackfin Processor Programming Reference
http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf
The Blackfin processor is already supported by major releases of gcc, and
there are binary and source rpms/tarballs for many architectures at:
http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete
documentation, including "getting started" guides available at:
http://docs.blackfin.uclinux.org/ which provides links to the sources and
patches you will need in order to set up a cross-compiling environment for
bfin-linux-uclibc
This patch, as well as the other patches (toolchain, distribution,
uClibc) are actively supported by Analog Devices Inc, at:
http://blackfin.uclinux.org/
We have tested this on LTP, and our test plan (including pass/fails) can
be found at:
http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel
[m.kozlowski@tuxland.pl: balance parenthesis in blackfin header files]
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
Signed-off-by: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Signed-off-by: Aubrey Li <aubrey.li@analog.com>
Signed-off-by: Jie Zhang <jie.zhang@analog.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-07 05:50:22 +08:00
|
|
|
depends on ARM || ARM26 || AVR32 || M32R || M68K || SPARC32 || SPARC64 || FRV || SUPERH || GENERIC_BUG || BFIN
|
2005-04-17 06:20:36 +08: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.
|
2007-03-28 05:21:33 +08:00
|
|
|
This adds debug symbols to the kernel and modules (gcc -g), and
|
|
|
|
|
is needed if you intend to use kernel crashdump or binary object
|
|
|
|
|
tools like crash, kgdb, LKCD, gdb, etc on the kernel.
|
2005-04-17 06:20:36 +08:00
|
|
|
Say Y here only if you plan to debug the kernel.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2005-10-31 07:03:12 +08:00
|
|
|
config DEBUG_VM
|
|
|
|
|
bool "Debug VM"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
2006-01-06 16:10:58 +08:00
|
|
|
Enable this to turn on extended checks in the virtual-memory system
|
|
|
|
|
that may impact performance.
|
2005-10-31 07:03:12 +08:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2006-09-29 16:59:00 +08:00
|
|
|
config DEBUG_LIST
|
|
|
|
|
bool "Debug linked list manipulation"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on extended checks in the linked-list
|
|
|
|
|
walking routines.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
config FRAME_POINTER
|
|
|
|
|
bool "Compile the kernel with frame pointers"
|
blackfin architecture
This adds support for the Analog Devices Blackfin processor architecture, and
currently supports the BF533, BF532, BF531, BF537, BF536, BF534, and BF561
(Dual Core) devices, with a variety of development platforms including those
avaliable from Analog Devices (BF533-EZKit, BF533-STAMP, BF537-STAMP,
BF561-EZKIT), and Bluetechnix! Tinyboards.
The Blackfin architecture was jointly developed by Intel and Analog Devices
Inc. (ADI) as the Micro Signal Architecture (MSA) core and introduced it in
December of 2000. Since then ADI has put this core into its Blackfin
processor family of devices. The Blackfin core has the advantages of a clean,
orthogonal,RISC-like microprocessor instruction set. It combines a dual-MAC
(Multiply/Accumulate), state-of-the-art signal processing engine and
single-instruction, multiple-data (SIMD) multimedia capabilities into a single
instruction-set architecture.
The Blackfin architecture, including the instruction set, is described by the
ADSP-BF53x/BF56x Blackfin Processor Programming Reference
http://blackfin.uclinux.org/gf/download/frsrelease/29/2549/Blackfin_PRM.pdf
The Blackfin processor is already supported by major releases of gcc, and
there are binary and source rpms/tarballs for many architectures at:
http://blackfin.uclinux.org/gf/project/toolchain/frs There is complete
documentation, including "getting started" guides available at:
http://docs.blackfin.uclinux.org/ which provides links to the sources and
patches you will need in order to set up a cross-compiling environment for
bfin-linux-uclibc
This patch, as well as the other patches (toolchain, distribution,
uClibc) are actively supported by Analog Devices Inc, at:
http://blackfin.uclinux.org/
We have tested this on LTP, and our test plan (including pass/fails) can
be found at:
http://docs.blackfin.uclinux.org/doku.php?id=testing_the_linux_kernel
[m.kozlowski@tuxland.pl: balance parenthesis in blackfin header files]
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
Signed-off-by: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Signed-off-by: Aubrey Li <aubrey.li@analog.com>
Signed-off-by: Jie Zhang <jie.zhang@analog.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-05-07 05:50:22 +08:00
|
|
|
depends on DEBUG_KERNEL && (X86 || CRIS || M68K || M68KNOMMU || FRV || UML || S390 || AVR32 || SUPERH || BFIN)
|
2005-05-29 06:51:59 +08:00
|
|
|
default y if DEBUG_INFO && UML
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here the resulting kernel image will be slightly larger
|
2005-10-31 07:02:51 +08:00
|
|
|
and slower, but it might give very useful debugging information on
|
|
|
|
|
some architectures or if you use external debuggers.
|
2005-09-13 00:49:25 +08:00
|
|
|
If you don't debug the kernel, you can say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2006-01-15 05:21:33 +08: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-31 07:03:12 +08: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.
|
2006-10-02 17:17:36 +08:00
|
|
|
|
|
|
|
|
config LKDTM
|
|
|
|
|
tristate "Linux Kernel Dump Test Tool Module"
|
2006-12-10 18:18:37 +08:00
|
|
|
depends on DEBUG_KERNEL
|
2006-10-02 17:17:36 +08:00
|
|
|
depends on KPROBES
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This module enables testing of the different dumping mechanisms by
|
|
|
|
|
inducing system failures at predefined crash points.
|
|
|
|
|
If you don't need it: say N
|
|
|
|
|
Choose M here to compile this code as a module. The module will be
|
|
|
|
|
called lkdtm.
|
|
|
|
|
|
|
|
|
|
Documentation on how to use the module can be found in
|
|
|
|
|
drivers/misc/lkdtm.c
|
2006-12-08 18:39:43 +08:00
|
|
|
|
|
|
|
|
config FAULT_INJECTION
|
2006-12-08 18:39:49 +08:00
|
|
|
bool "Fault-injection framework"
|
|
|
|
|
depends on DEBUG_KERNEL
|
2006-12-08 18:39:48 +08:00
|
|
|
help
|
|
|
|
|
Provide fault-injection framework.
|
|
|
|
|
For more details, see Documentation/fault-injection/.
|
2006-12-08 18:39:43 +08:00
|
|
|
|
2006-12-08 18:39:44 +08:00
|
|
|
config FAILSLAB
|
2006-12-08 18:39:49 +08:00
|
|
|
bool "Fault-injection capability for kmalloc"
|
|
|
|
|
depends on FAULT_INJECTION
|
2006-12-08 18:39:44 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for kmalloc.
|
2006-12-08 18:39:44 +08:00
|
|
|
|
2006-12-08 18:39:45 +08:00
|
|
|
config FAIL_PAGE_ALLOC
|
|
|
|
|
bool "Fault-injection capabilitiy for alloc_pages()"
|
2006-12-08 18:39:49 +08:00
|
|
|
depends on FAULT_INJECTION
|
2006-12-08 18:39:45 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for alloc_pages().
|
2006-12-08 18:39:45 +08:00
|
|
|
|
2006-12-08 18:39:46 +08:00
|
|
|
config FAIL_MAKE_REQUEST
|
2006-12-13 03:16:36 +08:00
|
|
|
bool "Fault-injection capability for disk IO"
|
2006-12-08 18:39:49 +08:00
|
|
|
depends on FAULT_INJECTION
|
2006-12-08 18:39:46 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Provide fault-injection capability for disk IO.
|
2006-12-08 18:39:46 +08:00
|
|
|
|
2006-12-08 18:39:43 +08:00
|
|
|
config FAULT_INJECTION_DEBUG_FS
|
|
|
|
|
bool "Debugfs entries for fault-injection capabilities"
|
2006-12-08 18:39:49 +08:00
|
|
|
depends on FAULT_INJECTION && SYSFS && DEBUG_FS
|
2006-12-08 18:39:43 +08:00
|
|
|
help
|
2006-12-08 18:39:49 +08:00
|
|
|
Enable configuration of fault-injection capabilities via debugfs.
|
2007-02-21 05:57:56 +08:00
|
|
|
|
|
|
|
|
config FAULT_INJECTION_STACKTRACE_FILTER
|
|
|
|
|
bool "stacktrace filter for fault-injection capabilities"
|
|
|
|
|
depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
|
|
|
|
|
select STACKTRACE
|
|
|
|
|
select FRAME_POINTER
|
|
|
|
|
help
|
|
|
|
|
Provide stacktrace filter for fault-injection capabilities
|