2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
config PRINTK_TIME
|
|
|
|
|
bool "Show timing information on printks"
|
2006-12-07 04:36:38 +00:00
|
|
|
depends on PRINTK
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
2012-05-10 02:30:45 +00:00
|
|
|
Selecting this option causes time stamps of the printk()
|
|
|
|
|
messages to be added to the output of the syslog() system
|
|
|
|
|
call and at the console.
|
|
|
|
|
|
|
|
|
|
The timestamp is always recorded internally, and exported
|
|
|
|
|
to /dev/kmsg. This flag just specifies if the timestamp should
|
|
|
|
|
be included, not that the timestamp is recorded.
|
|
|
|
|
|
|
|
|
|
The behavior is also controlled by the kernel command line
|
|
|
|
|
parameter printk.time=1. See Documentation/kernel-parameters.txt
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-03-22 23:34:23 +00:00
|
|
|
config DEFAULT_MESSAGE_LOGLEVEL
|
|
|
|
|
int "Default message log level (1-7)"
|
|
|
|
|
range 1 7
|
|
|
|
|
default "4"
|
|
|
|
|
help
|
|
|
|
|
Default log level for printk statements with no specified priority.
|
|
|
|
|
|
|
|
|
|
This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
|
|
|
|
|
that are auditing their logs closely may want to set it to a lower
|
|
|
|
|
priority.
|
|
|
|
|
|
2007-10-25 08:06:13 +00:00
|
|
|
config ENABLE_WARN_DEPRECATED
|
|
|
|
|
bool "Enable __deprecated logic"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable the __deprecated logic in the kernel build.
|
|
|
|
|
Disable this to suppress the "warning: 'foo' is deprecated
|
|
|
|
|
(declared at kernel/power/somefile.c:1234)" messages.
|
|
|
|
|
|
2006-08-15 05:43:18 +00: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-16 22:20:36 +00:00
|
|
|
|
2008-02-22 14:15:03 +00:00
|
|
|
config FRAME_WARN
|
|
|
|
|
int "Warn for stack frames larger than (needs gcc 4.4)"
|
|
|
|
|
range 0 8192
|
|
|
|
|
default 1024 if !64BIT
|
|
|
|
|
default 2048 if 64BIT
|
|
|
|
|
help
|
|
|
|
|
Tell gcc to warn at build time for stack frames larger than this.
|
|
|
|
|
Setting this too low will cause a lot of warnings.
|
|
|
|
|
Setting it to 0 disables the warning.
|
|
|
|
|
Requires gcc 4.4
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MAGIC_SYSRQ
|
|
|
|
|
bool "Magic SysRq key"
|
2006-01-10 04:54:51 +00:00
|
|
|
depends on !UML
|
2005-04-16 22:20:36 +00: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.
|
|
|
|
|
|
2009-09-18 19:49:22 +00:00
|
|
|
config STRIP_ASM_SYMS
|
|
|
|
|
bool "Strip assembler-generated symbols during link"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Strip internal assembler-generated symbols during a link (symbols
|
|
|
|
|
that look like '.Lxxx') so they don't pollute the output of
|
|
|
|
|
get_wchan() and suchlike.
|
|
|
|
|
|
2012-03-28 18:51:18 +00:00
|
|
|
config READABLE_ASM
|
|
|
|
|
bool "Generate readable assembler code"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Disable some compiler optimizations that tend to generate human unreadable
|
|
|
|
|
assembler output. This may make the kernel slightly slower, but it helps
|
|
|
|
|
to keep kernel developers who have to stare a lot at assembler listings
|
|
|
|
|
sane.
|
|
|
|
|
|
2006-06-28 11:26:45 +00: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 10:18:37 +00:00
|
|
|
config DEBUG_FS
|
|
|
|
|
bool "Debug Filesystem"
|
|
|
|
|
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.
|
|
|
|
|
|
2008-05-19 22:06:00 +00:00
|
|
|
For detailed documentation on the debugfs API, see
|
|
|
|
|
Documentation/DocBook/filesystems.
|
|
|
|
|
|
2006-12-10 10:18:37 +00:00
|
|
|
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.
|
|
|
|
|
|
2008-01-21 20:31:44 +00:00
|
|
|
config DEBUG_SECTION_MISMATCH
|
|
|
|
|
bool "Enable full Section mismatch analysis"
|
|
|
|
|
help
|
|
|
|
|
The section mismatch analysis checks if there are illegal
|
|
|
|
|
references from one section to another section.
|
2011-04-17 04:08:48 +00:00
|
|
|
During linktime or runtime, some sections are dropped;
|
|
|
|
|
any use of code/data previously in these sections would
|
2008-01-21 20:31:44 +00:00
|
|
|
most likely result in an oops.
|
2011-04-17 04:08:48 +00:00
|
|
|
In the code, functions and variables are annotated with
|
2012-12-21 23:16:45 +00:00
|
|
|
__init, __cpuinit, etc. (see the full list in include/linux/init.h),
|
2008-01-30 10:13:23 +00:00
|
|
|
which results in the code/data being placed in specific sections.
|
2011-04-17 04:08:48 +00:00
|
|
|
The section mismatch analysis is always performed after a full
|
|
|
|
|
kernel build, and enabling this option causes the following
|
|
|
|
|
additional steps to occur:
|
|
|
|
|
- Add the option -fno-inline-functions-called-once to gcc commands.
|
|
|
|
|
When inlining a function annotated with __init in a non-init
|
|
|
|
|
function, we would lose the section information and thus
|
2008-01-21 20:31:44 +00:00
|
|
|
the analysis would not catch the illegal reference.
|
2011-04-17 04:08:48 +00:00
|
|
|
This option tells gcc to inline less (but it does result in
|
|
|
|
|
a larger kernel).
|
|
|
|
|
- Run the section mismatch analysis for each module/built-in.o file.
|
|
|
|
|
When we run the section mismatch analysis on vmlinux.o, we
|
2008-01-30 10:13:23 +00:00
|
|
|
lose valueble information about where the mismatch was
|
2008-01-21 20:31:44 +00:00
|
|
|
introduced.
|
|
|
|
|
Running the analysis for each module/built-in.o file
|
2011-04-17 04:08:48 +00:00
|
|
|
tells where the mismatch happens much closer to the
|
|
|
|
|
source. The drawback is that the same mismatch is
|
|
|
|
|
reported at least twice.
|
|
|
|
|
- Enable verbose reporting from modpost in order to help resolve
|
|
|
|
|
the section mismatches that are reported.
|
2008-01-21 20:31:44 +00:00
|
|
|
|
2006-01-10 04:54:51 +00: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 08:52:00 +00: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.
|
|
|
|
|
|
2010-05-07 21:11:44 +00:00
|
|
|
config LOCKUP_DETECTOR
|
|
|
|
|
bool "Detect Hard and Soft Lockups"
|
2006-10-11 08:20:44 +00:00
|
|
|
depends on DEBUG_KERNEL && !S390
|
2005-09-06 22:16:27 +00:00
|
|
|
help
|
2010-05-07 21:11:44 +00:00
|
|
|
Say Y here to enable the kernel to act as a watchdog to detect
|
|
|
|
|
hard and soft lockups.
|
|
|
|
|
|
|
|
|
|
Softlockups are bugs that cause the kernel to loop in kernel
|
2012-02-09 22:42:21 +00:00
|
|
|
mode for more than 20 seconds, without giving other tasks a
|
2010-05-07 21:11:44 +00:00
|
|
|
chance to run. The current stack trace is displayed upon
|
|
|
|
|
detection and the system will stay locked up.
|
2005-09-06 22:16:27 +00:00
|
|
|
|
2010-05-07 21:11:44 +00:00
|
|
|
Hardlockups are bugs that cause the CPU to loop in kernel mode
|
2012-02-09 22:42:21 +00:00
|
|
|
for more than 10 seconds, without letting other interrupts have a
|
2010-05-07 21:11:44 +00:00
|
|
|
chance to run. The current stack trace is displayed upon detection
|
|
|
|
|
and the system will stay locked up.
|
2005-09-06 22:16:27 +00:00
|
|
|
|
2010-05-07 21:11:44 +00:00
|
|
|
The overhead should be minimal. A periodic hrtimer runs to
|
2012-02-09 22:42:21 +00:00
|
|
|
generate interrupts and kick the watchdog task every 4 seconds.
|
|
|
|
|
An NMI is generated every 10 seconds or so to check for hardlockups.
|
|
|
|
|
|
|
|
|
|
The frequency of hrtimer and NMI events and the soft and hard lockup
|
|
|
|
|
thresholds can be controlled through the sysctl watchdog_thresh.
|
2005-09-06 22:16:27 +00:00
|
|
|
|
2010-05-15 21:15:20 +00:00
|
|
|
config HARDLOCKUP_DETECTOR
|
2012-10-05 00:13:17 +00:00
|
|
|
def_bool y
|
|
|
|
|
depends on LOCKUP_DETECTOR && !HAVE_NMI_WATCHDOG
|
|
|
|
|
depends on PERF_EVENTS && HAVE_PERF_EVENTS_NMI
|
2005-09-06 22:16:27 +00:00
|
|
|
|
2011-03-22 23:34:16 +00:00
|
|
|
config BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
|
bool "Panic (Reboot) On Hard Lockups"
|
2012-10-05 00:13:17 +00:00
|
|
|
depends on HARDLOCKUP_DETECTOR
|
2011-03-22 23:34:16 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to enable the kernel to panic on "hard lockups",
|
|
|
|
|
which are bugs that cause the kernel to loop in kernel
|
2012-02-09 22:42:21 +00:00
|
|
|
mode with interrupts disabled for more than 10 seconds (configurable
|
|
|
|
|
using the watchdog_thresh sysctl).
|
2011-03-22 23:34:16 +00:00
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
|
|
config BOOTPARAM_HARDLOCKUP_PANIC_VALUE
|
|
|
|
|
int
|
2012-10-05 00:13:17 +00:00
|
|
|
depends on HARDLOCKUP_DETECTOR
|
2011-03-22 23:34:16 +00:00
|
|
|
range 0 1
|
|
|
|
|
default 0 if !BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
|
default 1 if BOOTPARAM_HARDLOCKUP_PANIC
|
|
|
|
|
|
2008-05-12 19:21:04 +00:00
|
|
|
config BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
|
bool "Panic (Reboot) On Soft Lockups"
|
2010-05-12 22:27:20 +00:00
|
|
|
depends on LOCKUP_DETECTOR
|
2008-05-12 19:21:04 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to enable the kernel to panic on "soft lockups",
|
|
|
|
|
which are bugs that cause the kernel to loop in kernel
|
2012-02-09 22:42:21 +00:00
|
|
|
mode for more than 20 seconds (configurable using the watchdog_thresh
|
|
|
|
|
sysctl), without giving other tasks a chance to run.
|
2008-05-12 19:21:04 +00:00
|
|
|
|
|
|
|
|
The panic can be used in combination with panic_timeout,
|
|
|
|
|
to cause the system to reboot automatically after a
|
|
|
|
|
lockup has been detected. This feature is useful for
|
|
|
|
|
high-availability systems that have uptime guarantees and
|
|
|
|
|
where a lockup must be resolved ASAP.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
|
|
config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
|
|
|
|
|
int
|
2010-05-15 20:30:22 +00:00
|
|
|
depends on LOCKUP_DETECTOR
|
2008-05-12 19:21:04 +00:00
|
|
|
range 0 1
|
|
|
|
|
default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
|
default 1 if BOOTPARAM_SOFTLOCKUP_PANIC
|
|
|
|
|
|
2012-04-11 12:15:29 +00:00
|
|
|
config PANIC_ON_OOPS
|
2013-02-22 00:43:04 +00:00
|
|
|
bool "Panic on Oops"
|
2012-04-11 12:15:29 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to enable the kernel to panic when it oopses. This
|
|
|
|
|
has the same effect as setting oops=panic on the kernel command
|
|
|
|
|
line.
|
|
|
|
|
|
|
|
|
|
This feature is useful to ensure that the kernel does not do
|
|
|
|
|
anything erroneous after an oops which could result in data
|
|
|
|
|
corruption or other issues.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
|
|
config PANIC_ON_OOPS_VALUE
|
|
|
|
|
int
|
|
|
|
|
range 0 1
|
|
|
|
|
default 0 if !PANIC_ON_OOPS
|
|
|
|
|
default 1 if PANIC_ON_OOPS
|
|
|
|
|
|
2009-01-15 19:08:40 +00:00
|
|
|
config DETECT_HUNG_TASK
|
|
|
|
|
bool "Detect Hung Tasks"
|
|
|
|
|
depends on DEBUG_KERNEL
|
2011-07-05 03:32:40 +00:00
|
|
|
default LOCKUP_DETECTOR
|
2009-01-15 19:08:40 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to enable the kernel to detect "hung tasks",
|
|
|
|
|
which are bugs that cause the task to be stuck in
|
|
|
|
|
uninterruptible "D" state indefinitiley.
|
|
|
|
|
|
|
|
|
|
When a hung task is detected, the kernel will print the
|
|
|
|
|
current stack trace (which you should report), but the
|
|
|
|
|
task will stay in uninterruptible state. If lockdep is
|
|
|
|
|
enabled then all held locks will also be reported. This
|
|
|
|
|
feature has negligible overhead.
|
|
|
|
|
|
2011-04-27 18:27:24 +00:00
|
|
|
config DEFAULT_HUNG_TASK_TIMEOUT
|
|
|
|
|
int "Default timeout for hung task detection (in seconds)"
|
|
|
|
|
depends on DETECT_HUNG_TASK
|
|
|
|
|
default 120
|
|
|
|
|
help
|
|
|
|
|
This option controls the default timeout (in seconds) used
|
|
|
|
|
to determine when a task has become non-responsive and should
|
|
|
|
|
be considered hung.
|
|
|
|
|
|
2011-11-01 00:10:07 +00:00
|
|
|
It can be adjusted at runtime via the kernel.hung_task_timeout_secs
|
|
|
|
|
sysctl or by writing a value to
|
|
|
|
|
/proc/sys/kernel/hung_task_timeout_secs.
|
2011-04-27 18:27:24 +00:00
|
|
|
|
|
|
|
|
A timeout of 0 disables the check. The default is two minutes.
|
|
|
|
|
Keeping the default should be fine in most cases.
|
|
|
|
|
|
2009-01-15 19:08:40 +00:00
|
|
|
config BOOTPARAM_HUNG_TASK_PANIC
|
|
|
|
|
bool "Panic (Reboot) On Hung Tasks"
|
|
|
|
|
depends on DETECT_HUNG_TASK
|
|
|
|
|
help
|
|
|
|
|
Say Y here to enable the kernel to panic on "hung tasks",
|
|
|
|
|
which are bugs that cause the kernel to leave a task stuck
|
|
|
|
|
in uninterruptible "D" state.
|
|
|
|
|
|
|
|
|
|
The panic can be used in combination with panic_timeout,
|
|
|
|
|
to cause the system to reboot automatically after a
|
|
|
|
|
hung task has been detected. This feature is useful for
|
|
|
|
|
high-availability systems that have uptime guarantees and
|
|
|
|
|
where a hung tasks must be resolved ASAP.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
|
|
|
|
config BOOTPARAM_HUNG_TASK_PANIC_VALUE
|
|
|
|
|
int
|
|
|
|
|
depends on DETECT_HUNG_TASK
|
|
|
|
|
range 0 1
|
|
|
|
|
default 0 if !BOOTPARAM_HUNG_TASK_PANIC
|
|
|
|
|
default 1 if BOOTPARAM_HUNG_TASK_PANIC
|
|
|
|
|
|
2007-07-09 16:52:00 +00:00
|
|
|
config SCHED_DEBUG
|
|
|
|
|
bool "Collect scheduler debugging info"
|
|
|
|
|
depends on DEBUG_KERNEL && PROC_FS
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, the /proc/sched_debug file will be provided
|
|
|
|
|
that can help debug the scheduler. The runtime overhead of this
|
|
|
|
|
option is minimal.
|
|
|
|
|
|
2005-04-16 22:20:36 +00: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 09:28:13 +00: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
|
2007-06-01 07:47:16 +00:00
|
|
|
about timer usage patterns in kernel and userspace. This feature
|
|
|
|
|
is lightweight if enabled in the kernel config but not activated
|
|
|
|
|
(it defaults to deactivated on bootup and will only be activated
|
|
|
|
|
if some application like powertop activates it explicitly).
|
[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 09:28:13 +00:00
|
|
|
|
2008-04-30 07:55:01 +00:00
|
|
|
config DEBUG_OBJECTS
|
|
|
|
|
bool "Debug object operations"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
|
kernel to track the life time of various objects and validate
|
|
|
|
|
the operations on those objects.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OBJECTS_SELFTEST
|
|
|
|
|
bool "Debug objects selftest"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
This enables the selftest of the object debug code.
|
|
|
|
|
|
|
|
|
|
config DEBUG_OBJECTS_FREE
|
|
|
|
|
bool "Debug objects in freed memory"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
This enables checks whether a k/v free operation frees an area
|
|
|
|
|
which contains an object which has not been deactivated
|
|
|
|
|
properly. This can make kmalloc/kfree-intensive workloads
|
|
|
|
|
much slower.
|
|
|
|
|
|
2008-04-30 07:55:03 +00:00
|
|
|
config DEBUG_OBJECTS_TIMERS
|
|
|
|
|
bool "Debug timer objects"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
|
timer routines to track the life time of timer objects and
|
|
|
|
|
validate the timer operations.
|
|
|
|
|
|
2009-11-15 16:09:48 +00:00
|
|
|
config DEBUG_OBJECTS_WORK
|
|
|
|
|
bool "Debug work objects"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
|
work queue routines to track the life time of work objects and
|
|
|
|
|
validate the work operations.
|
|
|
|
|
|
2010-04-17 12:48:42 +00:00
|
|
|
config DEBUG_OBJECTS_RCU_HEAD
|
|
|
|
|
bool "Debug RCU callbacks objects"
|
2011-02-23 17:42:14 +00:00
|
|
|
depends on DEBUG_OBJECTS
|
2010-04-17 12:48:42 +00:00
|
|
|
help
|
|
|
|
|
Enable this to turn on debugging of RCU list heads (call_rcu() usage).
|
|
|
|
|
|
2010-10-26 21:23:05 +00:00
|
|
|
config DEBUG_OBJECTS_PERCPU_COUNTER
|
|
|
|
|
bool "Debug percpu counter objects"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, additional code will be inserted into the
|
|
|
|
|
percpu counter routines to track the life time of percpu counter
|
|
|
|
|
objects and validate the percpu counter operations.
|
|
|
|
|
|
2008-11-26 09:02:00 +00:00
|
|
|
config DEBUG_OBJECTS_ENABLE_DEFAULT
|
|
|
|
|
int "debug_objects bootup default value (0-1)"
|
|
|
|
|
range 0 1
|
|
|
|
|
default "1"
|
|
|
|
|
depends on DEBUG_OBJECTS
|
|
|
|
|
help
|
|
|
|
|
Debug objects boot parameter default value
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DEBUG_SLAB
|
2006-03-25 11:07:22 +00:00
|
|
|
bool "Debug slab memory allocations"
|
2008-04-03 22:51:41 +00:00
|
|
|
depends on DEBUG_KERNEL && SLAB && !KMEMCHECK
|
2005-04-16 22:20:36 +00: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 11:06:39 +00:00
|
|
|
config DEBUG_SLAB_LEAK
|
|
|
|
|
bool "Memory leak debugging"
|
|
|
|
|
depends on DEBUG_SLAB
|
|
|
|
|
|
2007-07-16 06:38:14 +00:00
|
|
|
config SLUB_DEBUG_ON
|
|
|
|
|
bool "SLUB debugging on by default"
|
2008-04-03 22:51:41 +00:00
|
|
|
depends on SLUB && SLUB_DEBUG && !KMEMCHECK
|
2007-07-16 06:38:14 +00:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Boot with debugging on by default. SLUB boots by default with
|
|
|
|
|
the runtime debug capabilities switched off. Enabling this is
|
|
|
|
|
equivalent to specifying the "slub_debug" parameter on boot.
|
|
|
|
|
There is no support for more fine grained debug control like
|
|
|
|
|
possible with slub_debug=xxx. SLUB debugging may be switched
|
|
|
|
|
off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
|
|
|
|
|
"slub_debug=-".
|
|
|
|
|
|
2008-02-08 01:47:41 +00:00
|
|
|
config SLUB_STATS
|
|
|
|
|
default n
|
|
|
|
|
bool "Enable SLUB performance statistics"
|
2010-10-05 18:57:26 +00:00
|
|
|
depends on SLUB && SYSFS
|
2008-02-08 01:47:41 +00:00
|
|
|
help
|
|
|
|
|
SLUB statistics are useful to debug SLUBs allocation behavior in
|
|
|
|
|
order find ways to optimize the allocator. This should never be
|
|
|
|
|
enabled for production use since keeping statistics slows down
|
|
|
|
|
the allocator by a few percentage points. The slabinfo command
|
|
|
|
|
supports the determination of the most active slabs to figure
|
|
|
|
|
out which slabs are relevant to a particular load.
|
|
|
|
|
Try running: slabinfo -DA
|
|
|
|
|
|
2012-10-08 23:28:11 +00:00
|
|
|
config HAVE_DEBUG_KMEMLEAK
|
|
|
|
|
bool
|
|
|
|
|
|
2009-06-11 12:24:13 +00:00
|
|
|
config DEBUG_KMEMLEAK
|
|
|
|
|
bool "Kernel memory leak detector"
|
2013-01-17 02:54:16 +00:00
|
|
|
depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK
|
2011-04-27 16:06:19 +00:00
|
|
|
select DEBUG_FS
|
2009-06-11 12:24:13 +00:00
|
|
|
select STACKTRACE if STACKTRACE_SUPPORT
|
|
|
|
|
select KALLSYMS
|
2009-11-06 23:33:45 +00:00
|
|
|
select CRC32
|
2009-06-11 12:24:13 +00:00
|
|
|
help
|
|
|
|
|
Say Y here if you want to enable the memory leak
|
|
|
|
|
detector. The memory allocation/freeing is traced in a way
|
|
|
|
|
similar to the Boehm's conservative garbage collector, the
|
|
|
|
|
difference being that the orphan objects are not freed but
|
|
|
|
|
only shown in /sys/kernel/debug/kmemleak. Enabling this
|
|
|
|
|
feature will introduce an overhead to memory
|
|
|
|
|
allocations. See Documentation/kmemleak.txt for more
|
|
|
|
|
details.
|
|
|
|
|
|
2009-06-23 13:40:27 +00:00
|
|
|
Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances
|
|
|
|
|
of finding leaks due to the slab objects poisoning.
|
|
|
|
|
|
2009-06-11 12:24:13 +00:00
|
|
|
In order to access the kmemleak file, debugfs needs to be
|
|
|
|
|
mounted (usually at /sys/kernel/debug).
|
|
|
|
|
|
2009-06-25 09:16:11 +00:00
|
|
|
config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
|
|
|
|
|
int "Maximum kmemleak early log entries"
|
|
|
|
|
depends on DEBUG_KMEMLEAK
|
2009-10-06 08:33:57 +00:00
|
|
|
range 200 40000
|
2009-06-25 09:16:11 +00:00
|
|
|
default 400
|
|
|
|
|
help
|
|
|
|
|
Kmemleak must track all the memory allocations to avoid
|
|
|
|
|
reporting false positives. Since memory may be allocated or
|
|
|
|
|
freed before kmemleak is initialised, an early log buffer is
|
|
|
|
|
used to store these actions. If kmemleak reports "early log
|
|
|
|
|
buffer exceeded", please increase this value.
|
|
|
|
|
|
2009-06-11 12:24:14 +00:00
|
|
|
config DEBUG_KMEMLEAK_TEST
|
|
|
|
|
tristate "Simple test for the kernel memory leak detector"
|
2011-04-04 22:06:44 +00:00
|
|
|
depends on DEBUG_KMEMLEAK && m
|
2009-06-11 12:24:14 +00:00
|
|
|
help
|
2011-04-04 22:06:44 +00:00
|
|
|
This option enables a module that explicitly leaks memory.
|
2009-06-11 12:24:14 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-07-19 10:54:17 +00:00
|
|
|
config DEBUG_KMEMLEAK_DEFAULT_OFF
|
|
|
|
|
bool "Default kmemleak to off"
|
|
|
|
|
depends on DEBUG_KMEMLEAK
|
|
|
|
|
help
|
|
|
|
|
Say Y here to disable kmemleak by default. It can then be enabled
|
|
|
|
|
on the command line via kmemleak=on.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DEBUG_PREEMPT
|
|
|
|
|
bool "Debug preemptible kernel"
|
2009-10-16 07:21:39 +00:00
|
|
|
depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
|
2005-04-16 22:20:36 +00: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 09:54:55 +00: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 09:54:56 +00:00
|
|
|
config RT_MUTEX_TESTER
|
|
|
|
|
bool "Built-in scriptable tester for rt-mutexes"
|
2006-06-27 09:55:00 +00:00
|
|
|
depends on DEBUG_KERNEL && RT_MUTEXES
|
2006-06-27 09:54:56 +00:00
|
|
|
help
|
|
|
|
|
This option enables a rt-mutex tester.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DEBUG_SPINLOCK
|
2006-07-03 07:24:55 +00:00
|
|
|
bool "Spinlock and rw-lock debugging: basic checks"
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on DEBUG_KERNEL
|
2012-03-22 09:55:08 +00:00
|
|
|
select UNINLINE_SPIN_UNLOCK
|
2005-04-16 22:20:36 +00:00
|
|
|
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 07:24:55 +00: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 07:24:32 +00:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 07:24:55 +00: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 07:24:32 +00:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 07:24:55 +00:00
|
|
|
select LOCKDEP
|
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
|
select DEBUG_LOCK_ALLOC
|
2010-08-31 20:35:20 +00:00
|
|
|
select TRACE_IRQFLAGS
|
2006-07-03 07:24:55 +00:00
|
|
|
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 07:24:32 +00:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
2006-07-03 07:24:55 +00:00
|
|
|
select STACKTRACE
|
2010-05-25 09:33:26 +00:00
|
|
|
select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 && !MICROBLAZE
|
2006-07-03 07:24:55 +00:00
|
|
|
select KALLSYMS
|
|
|
|
|
select KALLSYMS_ALL
|
|
|
|
|
|
2007-07-19 08:48:56 +00:00
|
|
|
config LOCK_STAT
|
2007-09-25 04:24:43 +00:00
|
|
|
bool "Lock usage statistics"
|
2007-07-19 08:48:56 +00:00
|
|
|
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
|
|
|
|
|
select LOCKDEP
|
|
|
|
|
select DEBUG_SPINLOCK
|
|
|
|
|
select DEBUG_MUTEXES
|
|
|
|
|
select DEBUG_LOCK_ALLOC
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This feature enables tracking lock contention points
|
|
|
|
|
|
2007-10-07 07:24:33 +00:00
|
|
|
For more details, see Documentation/lockstat.txt
|
|
|
|
|
|
2010-02-27 16:10:39 +00:00
|
|
|
This also enables lock events required by "perf lock",
|
|
|
|
|
subcommand of perf.
|
|
|
|
|
If you want to use "perf lock", you also need to turn on
|
|
|
|
|
CONFIG_EVENT_TRACING.
|
2010-02-04 07:08:15 +00:00
|
|
|
|
|
|
|
|
CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
|
2010-02-27 16:10:39 +00:00
|
|
|
(CONFIG_LOCKDEP defines "acquire" and "release" events.)
|
2010-02-04 07:08:15 +00:00
|
|
|
|
2006-07-03 07:24:55 +00:00
|
|
|
config DEBUG_LOCKDEP
|
|
|
|
|
bool "Lock dependency engine debugging"
|
2006-07-14 07:24:32 +00:00
|
|
|
depends on DEBUG_KERNEL && LOCKDEP
|
2006-07-03 07:24:55 +00: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
|
|
|
|
|
bool
|
2010-08-31 20:35:20 +00:00
|
|
|
help
|
|
|
|
|
Enables hooks to interrupt enabling and disabling for
|
|
|
|
|
either tracing or lock debugging.
|
2006-07-03 07:24:55 +00:00
|
|
|
|
2011-06-08 17:31:56 +00:00
|
|
|
config DEBUG_ATOMIC_SLEEP
|
|
|
|
|
bool "Sleep inside atomic section checking"
|
2011-06-07 23:51:02 +00:00
|
|
|
select PREEMPT_COUNT
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, various routines which may sleep will become very
|
2011-06-08 17:31:56 +00:00
|
|
|
noisy if they are called inside atomic sections: when a spinlock is
|
|
|
|
|
held, inside an rcu read side critical section, inside preempt disabled
|
|
|
|
|
sections, inside an interrupt, etc...
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2006-07-03 07:24:48 +00: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 07:24:38 +00:00
|
|
|
config STACKTRACE
|
|
|
|
|
bool
|
|
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
|
|
2011-05-25 00:13:36 +00:00
|
|
|
config DEBUG_STACK_USAGE
|
|
|
|
|
bool "Stack utilization instrumentation"
|
2012-12-05 11:34:13 +00:00
|
|
|
depends on DEBUG_KERNEL && !IA64 && !PARISC && !METAG
|
2011-05-25 00:13:36 +00:00
|
|
|
help
|
|
|
|
|
Enables the display of the minimum amount of free stack which each
|
|
|
|
|
task has ever had available in the sysrq-T and sysrq-P debug output.
|
|
|
|
|
|
|
|
|
|
This option will slow down process creation somewhat.
|
|
|
|
|
|
2005-04-16 22:20:36 +00: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.
|
|
|
|
|
|
2012-10-08 23:28:13 +00:00
|
|
|
config HAVE_DEBUG_BUGVERBOSE
|
|
|
|
|
bool
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DEBUG_BUGVERBOSE
|
2011-01-20 22:44:16 +00:00
|
|
|
bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
|
2012-10-08 23:28:13 +00:00
|
|
|
depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE)
|
2009-12-15 02:00:25 +00:00
|
|
|
default y
|
2005-04-16 22:20:36 +00:00
|
|
|
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-27 21:21:33 +00: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-16 22:20:36 +00:00
|
|
|
Say Y here only if you plan to debug the kernel.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-07-14 13:43:52 +00:00
|
|
|
config DEBUG_INFO_REDUCED
|
|
|
|
|
bool "Reduce debugging information"
|
|
|
|
|
depends on DEBUG_INFO
|
|
|
|
|
help
|
|
|
|
|
If you say Y here gcc is instructed to generate less debugging
|
|
|
|
|
information for structure types. This means that tools that
|
|
|
|
|
need full debugging information (like kgdb or systemtap) won't
|
|
|
|
|
be happy. But if you merely need debugging information to
|
|
|
|
|
resolve line numbers there is no loss. Advantage is that
|
|
|
|
|
build directory object sizes shrink dramatically over a full
|
|
|
|
|
DEBUG_INFO build and compile times are reduced too.
|
|
|
|
|
Only works with newer gcc versions.
|
|
|
|
|
|
2005-10-30 23:03:12 +00:00
|
|
|
config DEBUG_VM
|
|
|
|
|
bool "Debug VM"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
2006-01-06 08:10:58 +00:00
|
|
|
Enable this to turn on extended checks in the virtual-memory system
|
|
|
|
|
that may impact performance.
|
2005-10-30 23:03:12 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-10-08 23:31:45 +00:00
|
|
|
config DEBUG_VM_RB
|
|
|
|
|
bool "Debug VM red-black trees"
|
|
|
|
|
depends on DEBUG_VM
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on more extended checks in the virtual-memory
|
|
|
|
|
system that may impact performance.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-06-12 11:56:40 +00:00
|
|
|
config DEBUG_VIRTUAL
|
|
|
|
|
bool "Debug VM translations"
|
|
|
|
|
depends on DEBUG_KERNEL && X86
|
|
|
|
|
help
|
|
|
|
|
Enable some costly sanity checks in virtual to page code. This can
|
|
|
|
|
catch mistakes with virt_to_page() and friends.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-01-08 12:04:47 +00:00
|
|
|
config DEBUG_NOMMU_REGIONS
|
|
|
|
|
bool "Debug the global anon/private NOMMU mapping region tree"
|
|
|
|
|
depends on DEBUG_KERNEL && !MMU
|
|
|
|
|
help
|
|
|
|
|
This option causes the global tree of anonymous and private mapping
|
|
|
|
|
regions to be regularly checked for invalid topology.
|
|
|
|
|
|
2008-02-15 22:38:01 +00:00
|
|
|
config DEBUG_WRITECOUNT
|
|
|
|
|
bool "Debug filesystem writers count"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to catch wrong use of the writers count in struct
|
|
|
|
|
vfsmount. This will increase the size of each file struct by
|
|
|
|
|
32 bits.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-07-24 04:26:49 +00:00
|
|
|
config DEBUG_MEMORY_INIT
|
2011-01-20 22:44:16 +00:00
|
|
|
bool "Debug memory initialisation" if EXPERT
|
|
|
|
|
default !EXPERT
|
2008-07-24 04:26:49 +00:00
|
|
|
help
|
|
|
|
|
Enable this for additional checks during memory initialisation.
|
|
|
|
|
The sanity checks verify aspects of the VM such as the memory model
|
|
|
|
|
and other information provided by the architecture. Verbose
|
|
|
|
|
information will be printed at KERN_DEBUG loglevel depending
|
|
|
|
|
on the mminit_loglevel= command-line option.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y
|
|
|
|
|
|
2006-09-29 08:59:00 +00: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.
|
|
|
|
|
|
2010-10-26 21:23:05 +00:00
|
|
|
config TEST_LIST_SORT
|
|
|
|
|
bool "Linked list sorting test"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on 'list_sort()' function test. This test is
|
|
|
|
|
executed only once during system boot, so affects only boot time.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-10-22 18:01:06 +00:00
|
|
|
config DEBUG_SG
|
|
|
|
|
bool "Debug SG table operations"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on checks on scatter-gather tables. This can
|
|
|
|
|
help find problems with drivers that do not properly initialize
|
|
|
|
|
their sg tables.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-08-15 22:29:38 +00:00
|
|
|
config DEBUG_NOTIFIERS
|
|
|
|
|
bool "Debug notifier call chains"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on sanity checking for notifier call chains.
|
|
|
|
|
This is most useful for kernel developers to make sure that
|
|
|
|
|
modules properly unregister themselves from notifier chains.
|
|
|
|
|
This is a relatively cheap check but if you care about maximum
|
|
|
|
|
performance, say N.
|
|
|
|
|
|
2009-09-02 08:13:40 +00:00
|
|
|
config DEBUG_CREDENTIALS
|
|
|
|
|
bool "Debug credential management"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
Enable this to turn on some debug checking for credential
|
|
|
|
|
management. The additional code keeps track of the number of
|
|
|
|
|
pointers from task_structs to any given cred struct, and checks to
|
|
|
|
|
see that this number never exceeds the usage count of the cred
|
|
|
|
|
struct.
|
|
|
|
|
|
|
|
|
|
Furthermore, if SELinux is enabled, this also checks that the
|
|
|
|
|
security pointer in the cred struct is never seen to be invalid.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-01-16 18:23:35 +00:00
|
|
|
#
|
|
|
|
|
# Select this config option from the architecture Kconfig, if it
|
2011-08-22 03:02:13 +00:00
|
|
|
# is preferred to always offer frame pointers as a config
|
2009-01-16 18:23:35 +00:00
|
|
|
# option on the architecture (regardless of KERNEL_DEBUG):
|
|
|
|
|
#
|
|
|
|
|
config ARCH_WANT_FRAME_POINTERS
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config FRAME_POINTER
|
|
|
|
|
bool "Compile the kernel with frame pointers"
|
2008-02-08 12:19:31 +00:00
|
|
|
depends on DEBUG_KERNEL && \
|
2011-01-22 21:35:38 +00:00
|
|
|
(CRIS || M68K || FRV || UML || \
|
2012-12-05 11:34:13 +00:00
|
|
|
AVR32 || SUPERH || BLACKFIN || MN10300 || METAG) || \
|
2009-01-07 10:05:10 +00:00
|
|
|
ARCH_WANT_FRAME_POINTERS
|
|
|
|
|
default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
|
|
|
|
|
help
|
|
|
|
|
If you say Y here the resulting kernel image will be slightly
|
|
|
|
|
larger and slower, but it gives very useful debugging information
|
|
|
|
|
in case of kernel bugs. (precise oopses/stacktraces/warnings)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-10-16 08:23:46 +00:00
|
|
|
config BOOT_PRINTK_DELAY
|
|
|
|
|
bool "Delay each boot printk message by N milliseconds"
|
|
|
|
|
depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY
|
|
|
|
|
help
|
|
|
|
|
This build option allows you to read kernel boot messages
|
|
|
|
|
by inserting a short delay after each one. The delay is
|
|
|
|
|
specified in milliseconds on the kernel command line,
|
|
|
|
|
using "boot_delay=N".
|
|
|
|
|
|
|
|
|
|
It is likely that you would also need to use "lpj=M" to preset
|
|
|
|
|
the "loops per jiffie" value.
|
|
|
|
|
See a previous boot log for the "lpj" value to use for your
|
|
|
|
|
system, and then set "lpj=M" before setting "boot_delay=N".
|
|
|
|
|
NOTE: Using this option may adversely affect SMP systems.
|
|
|
|
|
I.e., processors other than the first one may not boot up.
|
2011-07-05 03:32:40 +00:00
|
|
|
BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
|
2007-10-16 08:23:46 +00:00
|
|
|
what it believes to be lockup conditions.
|
|
|
|
|
|
2013-01-07 16:19:23 +00:00
|
|
|
menu "RCU Debugging"
|
|
|
|
|
|
|
|
|
|
config PROVE_RCU
|
|
|
|
|
bool "RCU debugging: prove RCU correctness"
|
|
|
|
|
depends on PROVE_LOCKING
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This feature enables lockdep extensions that check for correct
|
|
|
|
|
use of RCU APIs. This is currently under development. Say Y
|
|
|
|
|
if you want to debug RCU usage or help work on the PROVE_RCU
|
|
|
|
|
feature.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
|
|
config PROVE_RCU_REPEATEDLY
|
|
|
|
|
bool "RCU debugging: don't disable PROVE_RCU on first splat"
|
|
|
|
|
depends on PROVE_RCU
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
By itself, PROVE_RCU will disable checking upon issuing the
|
|
|
|
|
first warning (or "splat"). This feature prevents such
|
|
|
|
|
disabling, allowing multiple RCU-lockdep warnings to be printed
|
|
|
|
|
on a single reboot.
|
|
|
|
|
|
|
|
|
|
Say Y to allow multiple RCU-lockdep warnings per boot.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
|
|
config PROVE_RCU_DELAY
|
|
|
|
|
bool "RCU debugging: preemptible RCU race provocation"
|
|
|
|
|
depends on DEBUG_KERNEL && PREEMPT_RCU
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
There is a class of races that involve an unlikely preemption
|
|
|
|
|
of __rcu_read_unlock() just after ->rcu_read_lock_nesting has
|
|
|
|
|
been set to INT_MIN. This feature inserts a delay at that
|
|
|
|
|
point to increase the probability of these races.
|
|
|
|
|
|
|
|
|
|
Say Y to increase probability of preemption of __rcu_read_unlock().
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
|
|
config SPARSE_RCU_POINTER
|
|
|
|
|
bool "RCU debugging: sparse-based checks for pointer usage"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This feature enables the __rcu sparse annotation for
|
|
|
|
|
RCU-protected pointers. This annotation will cause sparse
|
|
|
|
|
to flag any non-RCU used of annotated pointers. This can be
|
|
|
|
|
helpful when debugging RCU usage. Please note that this feature
|
|
|
|
|
is not intended to enforce code cleanliness; it is instead merely
|
|
|
|
|
a debugging aid.
|
|
|
|
|
|
|
|
|
|
Say Y to make sparse flag questionable use of RCU-protected pointers
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2005-10-30 23:03:12 +00: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.
|
|
|
|
|
|
2008-06-18 16:26:49 +00:00
|
|
|
Say Y here if you want RCU torture tests to be built into
|
|
|
|
|
the kernel.
|
2005-10-30 23:03:12 +00:00
|
|
|
Say M if you want the RCU torture tests to build as a module.
|
|
|
|
|
Say N if you are unsure.
|
2006-10-02 09:17:36 +00:00
|
|
|
|
2008-06-18 16:26:49 +00:00
|
|
|
config RCU_TORTURE_TEST_RUNNABLE
|
|
|
|
|
bool "torture tests for RCU runnable by default"
|
|
|
|
|
depends on RCU_TORTURE_TEST = y
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option provides a way to build the RCU torture tests
|
|
|
|
|
directly into the kernel without them starting up at boot
|
|
|
|
|
time. You can use /proc/sys/kernel/rcutorture_runnable
|
|
|
|
|
to manually override this setting. This /proc file is
|
|
|
|
|
available only when the RCU torture tests have been built
|
|
|
|
|
into the kernel.
|
|
|
|
|
|
|
|
|
|
Say Y here if you want the RCU torture tests to start during
|
|
|
|
|
boot (you probably don't).
|
|
|
|
|
Say N here if you want the RCU torture tests to start only
|
|
|
|
|
after being manually enabled via /proc.
|
|
|
|
|
|
2010-06-02 23:21:38 +00:00
|
|
|
config RCU_CPU_STALL_TIMEOUT
|
|
|
|
|
int "RCU CPU stall timeout in seconds"
|
2012-10-19 19:49:17 +00:00
|
|
|
depends on RCU_STALL_COMMON
|
2010-06-02 23:21:38 +00:00
|
|
|
range 3 300
|
2012-10-26 00:59:23 +00:00
|
|
|
default 21
|
2010-06-02 23:21:38 +00:00
|
|
|
help
|
|
|
|
|
If a given RCU grace period extends more than the specified
|
|
|
|
|
number of seconds, a CPU stall warning is printed. If the
|
|
|
|
|
RCU grace period persists, additional CPU stall warnings are
|
|
|
|
|
printed at more widely spaced intervals.
|
|
|
|
|
|
2010-02-23 01:05:05 +00:00
|
|
|
config RCU_CPU_STALL_VERBOSE
|
|
|
|
|
bool "Print additional per-task information for RCU_CPU_STALL_DETECTOR"
|
2011-02-09 01:14:39 +00:00
|
|
|
depends on TREE_PREEMPT_RCU
|
2010-04-13 19:22:33 +00:00
|
|
|
default y
|
2010-02-23 01:05:05 +00:00
|
|
|
help
|
|
|
|
|
This option causes RCU to printk detailed per-task information
|
|
|
|
|
for any tasks that are stalling the current RCU grace period.
|
2008-08-11 01:35:38 +00:00
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2010-02-23 01:05:05 +00:00
|
|
|
Say Y if you want to enable such checks.
|
|
|
|
|
|
2012-01-16 21:29:10 +00:00
|
|
|
config RCU_CPU_STALL_INFO
|
|
|
|
|
bool "Print additional diagnostics on RCU CPU stall"
|
|
|
|
|
depends on (TREE_RCU || TREE_PREEMPT_RCU) && DEBUG_KERNEL
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
For each stalled CPU that is aware of the current RCU grace
|
|
|
|
|
period, print out additional per-CPU diagnostic information
|
|
|
|
|
regarding scheduling-clock ticks, idle state, and,
|
|
|
|
|
for RCU_FAST_NO_HZ kernels, idle-entry state.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
|
|
|
|
Say Y if you want to enable such diagnostics.
|
|
|
|
|
|
2012-01-06 23:10:44 +00:00
|
|
|
config RCU_TRACE
|
|
|
|
|
bool "Enable tracing for RCU"
|
|
|
|
|
depends on DEBUG_KERNEL
|
2012-11-15 00:26:40 +00:00
|
|
|
select TRACE_CLOCK
|
2012-01-06 23:10:44 +00:00
|
|
|
help
|
|
|
|
|
This option provides tracing in RCU which presents stats
|
|
|
|
|
in debugfs for debugging RCU implementation.
|
|
|
|
|
|
|
|
|
|
Say Y here if you want to enable RCU tracing
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2013-01-07 16:19:23 +00:00
|
|
|
endmenu # "RCU Debugging"
|
|
|
|
|
|
2008-01-30 12:32:53 +00:00
|
|
|
config KPROBES_SANITY_TEST
|
|
|
|
|
bool "Kprobes sanity tests"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on KPROBES
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option provides for testing basic kprobes functionality on
|
|
|
|
|
boot. A sample kprobe, jprobe and kretprobe are inserted and
|
|
|
|
|
verified for functionality.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2008-01-30 12:33:08 +00:00
|
|
|
config BACKTRACE_SELF_TEST
|
|
|
|
|
tristate "Self test for the backtrace code"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option provides a kernel module that can be used to test
|
|
|
|
|
the kernel stack backtrace code. This option is not useful
|
|
|
|
|
for distributions or general kernels, but only for kernel
|
|
|
|
|
developers working on architecture code.
|
|
|
|
|
|
2008-06-27 16:04:48 +00:00
|
|
|
Note that if you want to also test saved backtraces, you will
|
|
|
|
|
have to enable STACKTRACE as well.
|
|
|
|
|
|
2008-01-30 12:33:08 +00:00
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2008-08-25 10:47:25 +00:00
|
|
|
config DEBUG_BLOCK_EXT_DEVT
|
|
|
|
|
bool "Force extended block device numbers and spread them"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on BLOCK
|
2008-08-29 07:06:29 +00:00
|
|
|
default n
|
2008-08-25 10:47:25 +00:00
|
|
|
help
|
2008-10-13 08:46:01 +00:00
|
|
|
BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
|
|
|
|
|
SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
|
|
|
|
|
YOU ARE DOING. Distros, please enable this and fix whatever
|
|
|
|
|
is broken.
|
|
|
|
|
|
2008-08-25 10:47:25 +00:00
|
|
|
Conventionally, block device numbers are allocated from
|
|
|
|
|
predetermined contiguous area. However, extended block area
|
|
|
|
|
may introduce non-contiguous block device numbers. This
|
|
|
|
|
option forces most block device numbers to be allocated from
|
|
|
|
|
the extended space and spreads them to discover kernel or
|
|
|
|
|
userland code paths which assume predetermined contiguous
|
|
|
|
|
device number allocation.
|
|
|
|
|
|
2008-09-01 11:44:35 +00:00
|
|
|
Note that turning on this debug option shuffles all the
|
|
|
|
|
device numbers for all IDE and SCSI devices including libata
|
|
|
|
|
ones, so root partition specified using device number
|
|
|
|
|
directly (via rdev or root=MAJ:MIN) won't work anymore.
|
|
|
|
|
Textual device names (root=/dev/sdXn) will continue to work.
|
|
|
|
|
|
2008-08-25 10:47:25 +00:00
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2009-06-24 06:13:50 +00:00
|
|
|
config DEBUG_FORCE_WEAK_PER_CPU
|
|
|
|
|
bool "Force weak per-cpu definitions"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
s390 and alpha require percpu variables in modules to be
|
|
|
|
|
defined weak to work around addressing range issue which
|
|
|
|
|
puts the following two restrictions on percpu variable
|
|
|
|
|
definitions.
|
|
|
|
|
|
|
|
|
|
1. percpu symbols must be unique whether static or not
|
|
|
|
|
2. percpu variables can't be defined inside a function
|
|
|
|
|
|
|
|
|
|
To ensure that generic code follows the above rules, this
|
|
|
|
|
option forces all percpu variables to be defined as weak.
|
|
|
|
|
|
2011-05-25 00:13:32 +00:00
|
|
|
config DEBUG_PER_CPU_MAPS
|
|
|
|
|
bool "Debug access to per_cpu maps"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on SMP
|
|
|
|
|
help
|
|
|
|
|
Say Y to verify that the per_cpu map being accessed has
|
|
|
|
|
been set up. This adds a fair amount of code to kernel memory
|
|
|
|
|
and decreases performance.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2006-10-02 09:17:36 +00:00
|
|
|
config LKDTM
|
|
|
|
|
tristate "Linux Kernel Dump Test Tool Module"
|
2010-03-05 21:42:49 +00:00
|
|
|
depends on DEBUG_FS
|
2008-02-23 23:23:26 +00:00
|
|
|
depends on BLOCK
|
2006-10-02 09:17:36 +00:00
|
|
|
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
|
2010-03-05 21:42:49 +00:00
|
|
|
Documentation/fault-injection/provoke-crashes.txt
|
2006-12-08 10:39:43 +00:00
|
|
|
|
2012-07-30 21:43:02 +00:00
|
|
|
config NOTIFIER_ERROR_INJECTION
|
|
|
|
|
tristate "Notifier error injection"
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
select DEBUG_FS
|
|
|
|
|
help
|
2012-11-30 07:44:39 +00:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-07-30 21:43:02 +00:00
|
|
|
specified notifier chain callbacks. It is useful to test the error
|
|
|
|
|
handling of notifier call chain failures.
|
|
|
|
|
|
|
|
|
|
Say N if unsure.
|
|
|
|
|
|
2010-05-26 21:43:36 +00:00
|
|
|
config CPU_NOTIFIER_ERROR_INJECT
|
|
|
|
|
tristate "CPU notifier error injection module"
|
2012-07-30 21:43:03 +00:00
|
|
|
depends on HOTPLUG_CPU && NOTIFIER_ERROR_INJECTION
|
2010-05-26 21:43:36 +00:00
|
|
|
help
|
|
|
|
|
This option provides a kernel module that can be used to test
|
2012-11-30 07:44:39 +00:00
|
|
|
the error handling of the cpu notifiers by injecting artificial
|
2012-07-30 21:43:03 +00:00
|
|
|
errors to CPU notifier chain callbacks. It is controlled through
|
|
|
|
|
debugfs interface under /sys/kernel/debug/notifier-error-inject/cpu
|
|
|
|
|
|
|
|
|
|
If the notifier call chain should be failed with some events
|
|
|
|
|
notified, write the error code to "actions/<notifier event>/error".
|
|
|
|
|
|
|
|
|
|
Example: Inject CPU offline error (-1 == -EPERM)
|
|
|
|
|
|
|
|
|
|
# cd /sys/kernel/debug/notifier-error-inject/cpu
|
|
|
|
|
# echo -1 > actions/CPU_DOWN_PREPARE/error
|
|
|
|
|
# echo 0 > /sys/devices/system/cpu/cpu1/online
|
|
|
|
|
bash: echo: write error: Operation not permitted
|
2010-05-26 21:43:36 +00:00
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called cpu-notifier-error-inject.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-07-30 21:43:07 +00:00
|
|
|
config PM_NOTIFIER_ERROR_INJECT
|
|
|
|
|
tristate "PM notifier error injection module"
|
|
|
|
|
depends on PM && NOTIFIER_ERROR_INJECTION
|
|
|
|
|
default m if PM_DEBUG
|
|
|
|
|
help
|
2012-11-30 07:44:39 +00:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-07-30 21:43:07 +00:00
|
|
|
PM notifier chain callbacks. It is controlled through debugfs
|
|
|
|
|
interface /sys/kernel/debug/notifier-error-inject/pm
|
|
|
|
|
|
|
|
|
|
If the notifier call chain should be failed with some events
|
|
|
|
|
notified, write the error code to "actions/<notifier event>/error".
|
|
|
|
|
|
|
|
|
|
Example: Inject PM suspend error (-12 = -ENOMEM)
|
|
|
|
|
|
|
|
|
|
# cd /sys/kernel/debug/notifier-error-inject/pm/
|
|
|
|
|
# echo -12 > actions/PM_SUSPEND_PREPARE/error
|
|
|
|
|
# echo mem > /sys/power/state
|
|
|
|
|
bash: echo: write error: Cannot allocate memory
|
|
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called pm-notifier-error-inject.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-07-30 21:43:10 +00:00
|
|
|
config MEMORY_NOTIFIER_ERROR_INJECT
|
|
|
|
|
tristate "Memory hotplug notifier error injection module"
|
|
|
|
|
depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION
|
|
|
|
|
help
|
2012-11-30 07:44:39 +00:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-07-30 21:43:10 +00:00
|
|
|
memory hotplug notifier chain callbacks. It is controlled through
|
|
|
|
|
debugfs interface under /sys/kernel/debug/notifier-error-inject/memory
|
|
|
|
|
|
|
|
|
|
If the notifier call chain should be failed with some events
|
|
|
|
|
notified, write the error code to "actions/<notifier event>/error".
|
|
|
|
|
|
|
|
|
|
Example: Inject memory hotplug offline error (-12 == -ENOMEM)
|
|
|
|
|
|
|
|
|
|
# cd /sys/kernel/debug/notifier-error-inject/memory
|
|
|
|
|
# echo -12 > actions/MEM_GOING_OFFLINE/error
|
|
|
|
|
# echo offline > /sys/devices/system/memory/memoryXXX/state
|
|
|
|
|
bash: echo: write error: Cannot allocate memory
|
|
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called pSeries-reconfig-notifier-error-inject.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-12-13 23:32:52 +00:00
|
|
|
config OF_RECONFIG_NOTIFIER_ERROR_INJECT
|
|
|
|
|
tristate "OF reconfig notifier error injection module"
|
|
|
|
|
depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION
|
2012-07-30 21:43:13 +00:00
|
|
|
help
|
2012-11-30 07:44:39 +00:00
|
|
|
This option provides the ability to inject artificial errors to
|
2012-12-13 23:32:52 +00:00
|
|
|
OF reconfig notifier chain callbacks. It is controlled
|
2012-07-30 21:43:13 +00:00
|
|
|
through debugfs interface under
|
2012-12-13 23:32:52 +00:00
|
|
|
/sys/kernel/debug/notifier-error-inject/OF-reconfig/
|
2012-07-30 21:43:13 +00:00
|
|
|
|
|
|
|
|
If the notifier call chain should be failed with some events
|
|
|
|
|
notified, write the error code to "actions/<notifier event>/error".
|
|
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called memory-notifier-error-inject.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2006-12-08 10:39:43 +00:00
|
|
|
config FAULT_INJECTION
|
2006-12-08 10:39:49 +00:00
|
|
|
bool "Fault-injection framework"
|
|
|
|
|
depends on DEBUG_KERNEL
|
2006-12-08 10:39:48 +00:00
|
|
|
help
|
|
|
|
|
Provide fault-injection framework.
|
|
|
|
|
For more details, see Documentation/fault-injection/.
|
2006-12-08 10:39:43 +00:00
|
|
|
|
2006-12-08 10:39:44 +00:00
|
|
|
config FAILSLAB
|
2006-12-08 10:39:49 +00:00
|
|
|
bool "Fault-injection capability for kmalloc"
|
|
|
|
|
depends on FAULT_INJECTION
|
2008-12-23 10:37:01 +00:00
|
|
|
depends on SLAB || SLUB
|
2006-12-08 10:39:44 +00:00
|
|
|
help
|
2006-12-08 10:39:49 +00:00
|
|
|
Provide fault-injection capability for kmalloc.
|
2006-12-08 10:39:44 +00:00
|
|
|
|
2006-12-08 10:39:45 +00:00
|
|
|
config FAIL_PAGE_ALLOC
|
|
|
|
|
bool "Fault-injection capabilitiy for alloc_pages()"
|
2006-12-08 10:39:49 +00:00
|
|
|
depends on FAULT_INJECTION
|
2006-12-08 10:39:45 +00:00
|
|
|
help
|
2006-12-08 10:39:49 +00:00
|
|
|
Provide fault-injection capability for alloc_pages().
|
2006-12-08 10:39:45 +00:00
|
|
|
|
2006-12-08 10:39:46 +00:00
|
|
|
config FAIL_MAKE_REQUEST
|
2006-12-12 19:16:36 +00:00
|
|
|
bool "Fault-injection capability for disk IO"
|
2008-09-14 12:56:33 +00:00
|
|
|
depends on FAULT_INJECTION && BLOCK
|
2006-12-08 10:39:46 +00:00
|
|
|
help
|
2006-12-08 10:39:49 +00:00
|
|
|
Provide fault-injection capability for disk IO.
|
2006-12-08 10:39:46 +00:00
|
|
|
|
2008-09-14 12:56:33 +00:00
|
|
|
config FAIL_IO_TIMEOUT
|
2010-07-21 07:05:53 +00:00
|
|
|
bool "Fault-injection capability for faking disk interrupts"
|
2008-09-14 12:56:33 +00:00
|
|
|
depends on FAULT_INJECTION && BLOCK
|
|
|
|
|
help
|
|
|
|
|
Provide fault-injection capability on end IO handling. This
|
|
|
|
|
will make the block layer "forget" an interrupt as configured,
|
|
|
|
|
thus exercising the error handling.
|
|
|
|
|
|
|
|
|
|
Only works with drivers that use the generic timeout handling,
|
|
|
|
|
for others it wont do anything.
|
|
|
|
|
|
2011-08-19 12:52:37 +00:00
|
|
|
config FAIL_MMC_REQUEST
|
|
|
|
|
bool "Fault-injection capability for MMC IO"
|
|
|
|
|
select DEBUG_FS
|
|
|
|
|
depends on FAULT_INJECTION && MMC
|
|
|
|
|
help
|
|
|
|
|
Provide fault-injection capability for MMC IO.
|
|
|
|
|
This will make the mmc core return data errors. This is
|
|
|
|
|
useful to test the error handling in the mmc block device
|
|
|
|
|
and to test how the mmc host driver handles retries from
|
|
|
|
|
the block device.
|
|
|
|
|
|
2006-12-08 10:39:43 +00:00
|
|
|
config FAULT_INJECTION_DEBUG_FS
|
|
|
|
|
bool "Debugfs entries for fault-injection capabilities"
|
2006-12-08 10:39:49 +00:00
|
|
|
depends on FAULT_INJECTION && SYSFS && DEBUG_FS
|
2006-12-08 10:39:43 +00:00
|
|
|
help
|
2006-12-08 10:39:49 +00:00
|
|
|
Enable configuration of fault-injection capabilities via debugfs.
|
2007-02-20 21:57:56 +00:00
|
|
|
|
|
|
|
|
config FAULT_INJECTION_STACKTRACE_FILTER
|
|
|
|
|
bool "stacktrace filter for fault-injection capabilities"
|
|
|
|
|
depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
|
2007-05-12 17:36:53 +00:00
|
|
|
depends on !X86_64
|
2007-02-20 21:57:56 +00:00
|
|
|
select STACKTRACE
|
2011-06-10 14:12:21 +00:00
|
|
|
select FRAME_POINTER if !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND
|
2007-02-20 21:57:56 +00:00
|
|
|
help
|
|
|
|
|
Provide stacktrace filter for fault-injection capabilities
|
2007-10-19 06:41:07 +00:00
|
|
|
|
2008-01-25 20:08:34 +00:00
|
|
|
config LATENCYTOP
|
|
|
|
|
bool "Latency measuring infrastructure"
|
2010-08-12 19:31:21 +00:00
|
|
|
depends on HAVE_LATENCYTOP_SUPPORT
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
depends on STACKTRACE_SUPPORT
|
|
|
|
|
depends on PROC_FS
|
2011-06-10 14:12:21 +00:00
|
|
|
select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM_UNWIND
|
2008-01-25 20:08:34 +00:00
|
|
|
select KALLSYMS
|
|
|
|
|
select KALLSYMS_ALL
|
|
|
|
|
select STACKTRACE
|
|
|
|
|
select SCHEDSTATS
|
|
|
|
|
select SCHED_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you want to use the LatencyTOP tool
|
|
|
|
|
to find out which userspace is blocking on what kernel operations.
|
|
|
|
|
|
2009-03-31 22:23:17 +00:00
|
|
|
source mm/Kconfig.debug
|
2008-05-12 19:20:42 +00:00
|
|
|
source kernel/trace/Kconfig
|
|
|
|
|
|
2012-10-08 23:30:39 +00:00
|
|
|
config RBTREE_TEST
|
|
|
|
|
tristate "Red-Black tree test"
|
|
|
|
|
depends on m && DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
A benchmark measuring the performance of the rbtree library.
|
|
|
|
|
Also includes rbtree invariant checks.
|
|
|
|
|
|
rbtree: add prio tree and interval tree tests
Patch 1 implements support for interval trees, on top of the augmented
rbtree API. It also adds synthetic tests to compare the performance of
interval trees vs prio trees. Short answers is that interval trees are
slightly faster (~25%) on insert/erase, and much faster (~2.4 - 3x)
on search. It is debatable how realistic the synthetic test is, and I have
not made such measurements yet, but my impression is that interval trees
would still come out faster.
Patch 2 uses a preprocessor template to make the interval tree generic,
and uses it as a replacement for the vma prio_tree.
Patch 3 takes the other prio_tree user, kmemleak, and converts it to use
a basic rbtree. We don't actually need the augmented rbtree support here
because the intervals are always non-overlapping.
Patch 4 removes the now-unused prio tree library.
Patch 5 proposes an additional optimization to rb_erase_augmented, now
providing it as an inline function so that the augmented callbacks can be
inlined in. This provides an additional 5-10% performance improvement
for the interval tree insert/erase benchmark. There is a maintainance cost
as it exposes augmented rbtree users to some of the rbtree library internals;
however I think this cost shouldn't be too high as I expect the augmented
rbtree will always have much less users than the base rbtree.
I should probably add a quick summary of why I think it makes sense to
replace prio trees with augmented rbtree based interval trees now. One of
the drivers is that we need augmented rbtrees for Rik's vma gap finding
code, and once you have them, it just makes sense to use them for interval
trees as well, as this is the simpler and more well known algorithm. prio
trees, in comparison, seem *too* clever: they impose an additional 'heap'
constraint on the tree, which they use to guarantee a faster worst-case
complexity of O(k+log N) for stabbing queries in a well-balanced prio
tree, vs O(k*log N) for interval trees (where k=number of matches,
N=number of intervals). Now this sounds great, but in practice prio trees
don't realize this theorical benefit. First, the additional constraint
makes them harder to update, so that the kernel implementation has to
simplify things by balancing them like a radix tree, which is not always
ideal. Second, the fact that there are both index and heap properties
makes both tree manipulation and search more complex, which results in a
higher multiplicative time constant. As it turns out, the simple interval
tree algorithm ends up running faster than the more clever prio tree.
This patch:
Add two test modules:
- prio_tree_test measures the performance of lib/prio_tree.c, both for
insertion/removal and for stabbing searches
- interval_tree_test measures the performance of a library of equivalent
functionality, built using the augmented rbtree support.
In order to support the second test module, lib/interval_tree.c is
introduced. It is kept separate from the interval_tree_test main file
for two reasons: first we don't want to provide an unfair advantage
over prio_tree_test by having everything in a single compilation unit,
and second there is the possibility that the interval tree functionality
could get some non-test users in kernel over time.
Signed-off-by: Michel Lespinasse <walken@google.com>
Cc: Rik van Riel <riel@redhat.com>
Cc: Hillf Danton <dhillf@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2012-10-08 23:31:23 +00:00
|
|
|
config INTERVAL_TREE_TEST
|
|
|
|
|
tristate "Interval tree test"
|
|
|
|
|
depends on m && DEBUG_KERNEL
|
|
|
|
|
help
|
|
|
|
|
A benchmark measuring the performance of the interval tree library
|
|
|
|
|
|
x86: early boot debugging via FireWire (ohci1394_dma=early)
This patch adds a new configuration option, which adds support for a new
early_param which gets checked in arch/x86/kernel/setup_{32,64}.c:setup_arch()
to decide wether OHCI-1394 FireWire controllers should be initialized and
enabled for physical DMA access to allow remote debugging of early problems
like issues ACPI or other subsystems which are executed very early.
If the config option is not enabled, no code is changed, and if the boot
paramenter is not given, no new code is executed, and independent of that,
all new code is freed after boot, so the config option can be even enabled
in standard, non-debug kernels.
With specialized tools, it is then possible to get debugging information
from machines which have no serial ports (notebooks) such as the printk
buffer contents, or any data which can be referenced from global pointers,
if it is stored below the 4GB limit and even memory dumps of of the physical
RAM region below the 4GB limit can be taken without any cooperation from the
CPU of the host, so the machine can be crashed early, it does not matter.
In the extreme, even kernel debuggers can be accessed in this way. I wrote
a small kgdb module and an accompanying gdb stub for FireWire which allows
to gdb to talk to kgdb using remote remory reads and writes over FireWire.
An version of the gdb stub fore FireWire is able to read all global data
from a system which is running a a normal kernel without any kernel debugger,
without any interruption or support of the system's CPU. That way, e.g. the
task struct and so on can be read and even manipulated when the physical DMA
access is granted.
A HOWTO is included in this patch, in Documentation/debugging-via-ohci1394.txt
and I've put a copy online at
ftp://ftp.suse.de/private/bk/firewire/docs/debugging-via-ohci1394.txt
It also has links to all the tools which are available to make use of it
another copy of it is online at:
ftp://ftp.suse.de/private/bk/firewire/kernel/ohci1394_dma_early-v2.diff
Signed-Off-By: Bernhard Kaindl <bk@suse.de>
Tested-By: Thomas Renninger <trenn@suse.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 12:34:11 +00:00
|
|
|
config PROVIDE_OHCI1394_DMA_INIT
|
2008-02-28 19:54:43 +00:00
|
|
|
bool "Remote debugging over FireWire early on boot"
|
x86: early boot debugging via FireWire (ohci1394_dma=early)
This patch adds a new configuration option, which adds support for a new
early_param which gets checked in arch/x86/kernel/setup_{32,64}.c:setup_arch()
to decide wether OHCI-1394 FireWire controllers should be initialized and
enabled for physical DMA access to allow remote debugging of early problems
like issues ACPI or other subsystems which are executed very early.
If the config option is not enabled, no code is changed, and if the boot
paramenter is not given, no new code is executed, and independent of that,
all new code is freed after boot, so the config option can be even enabled
in standard, non-debug kernels.
With specialized tools, it is then possible to get debugging information
from machines which have no serial ports (notebooks) such as the printk
buffer contents, or any data which can be referenced from global pointers,
if it is stored below the 4GB limit and even memory dumps of of the physical
RAM region below the 4GB limit can be taken without any cooperation from the
CPU of the host, so the machine can be crashed early, it does not matter.
In the extreme, even kernel debuggers can be accessed in this way. I wrote
a small kgdb module and an accompanying gdb stub for FireWire which allows
to gdb to talk to kgdb using remote remory reads and writes over FireWire.
An version of the gdb stub fore FireWire is able to read all global data
from a system which is running a a normal kernel without any kernel debugger,
without any interruption or support of the system's CPU. That way, e.g. the
task struct and so on can be read and even manipulated when the physical DMA
access is granted.
A HOWTO is included in this patch, in Documentation/debugging-via-ohci1394.txt
and I've put a copy online at
ftp://ftp.suse.de/private/bk/firewire/docs/debugging-via-ohci1394.txt
It also has links to all the tools which are available to make use of it
another copy of it is online at:
ftp://ftp.suse.de/private/bk/firewire/kernel/ohci1394_dma_early-v2.diff
Signed-Off-By: Bernhard Kaindl <bk@suse.de>
Tested-By: Thomas Renninger <trenn@suse.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 12:34:11 +00:00
|
|
|
depends on PCI && X86
|
|
|
|
|
help
|
|
|
|
|
If you want to debug problems which hang or crash the kernel early
|
|
|
|
|
on boot and the crashing machine has a FireWire port, you can use
|
|
|
|
|
this feature to remotely access the memory of the crashed machine
|
|
|
|
|
over FireWire. This employs remote DMA as part of the OHCI1394
|
|
|
|
|
specification which is now the standard for FireWire controllers.
|
|
|
|
|
|
|
|
|
|
With remote DMA, you can monitor the printk buffer remotely using
|
|
|
|
|
firescope and access all memory below 4GB using fireproxy from gdb.
|
|
|
|
|
Even controlling a kernel debugger is possible using remote DMA.
|
|
|
|
|
|
|
|
|
|
Usage:
|
|
|
|
|
|
|
|
|
|
If ohci1394_dma=early is used as boot parameter, it will initialize
|
|
|
|
|
all OHCI1394 controllers which are found in the PCI config space.
|
|
|
|
|
|
|
|
|
|
As all changes to the FireWire bus such as enabling and disabling
|
|
|
|
|
devices cause a bus reset and thereby disable remote DMA for all
|
|
|
|
|
devices, be sure to have the cable plugged and FireWire enabled on
|
|
|
|
|
the debugging host before booting the debug target for debugging.
|
|
|
|
|
|
|
|
|
|
This code (~1k) is freed after boot. By then, the firewire stack
|
|
|
|
|
in charge of the OHCI-1394 controllers should be used instead.
|
|
|
|
|
|
|
|
|
|
See Documentation/debugging-via-ohci1394.txt for more information.
|
2008-01-25 20:08:34 +00:00
|
|
|
|
2008-02-28 19:54:43 +00:00
|
|
|
config FIREWIRE_OHCI_REMOTE_DMA
|
|
|
|
|
bool "Remote debugging over FireWire with firewire-ohci"
|
|
|
|
|
depends on FIREWIRE_OHCI
|
|
|
|
|
help
|
|
|
|
|
This option lets you use the FireWire bus for remote debugging
|
|
|
|
|
with help of the firewire-ohci driver. It enables unfiltered
|
|
|
|
|
remote DMA in firewire-ohci.
|
|
|
|
|
See Documentation/debugging-via-ohci1394.txt for more information.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2009-02-20 23:38:47 +00:00
|
|
|
config BUILD_DOCSRC
|
docsrc: build Documentation/ sources
Currently source files in the Documentation/ sub-dir can easily bit-rot
since they are not generally buildable, either because they are hidden in
text files or because there are no Makefile rules for them. This needs to
be fixed so that the source files remain usable and good examples of code
instead of bad examples.
Add the ability to build source files that are in the Documentation/ dir.
Add to Kconfig as "BUILD_DOCSRC" config symbol.
Use "CONFIG_BUILD_DOCSRC=1 make ..." to build objects from the
Documentation/ sources. Or enable BUILD_DOCSRC in the *config system.
However, this symbol depends on HEADERS_CHECK since the header files need
to be installed (for userspace builds).
Built (using cross-tools) for x86-64, i386, alpha, ia64, sparc32,
sparc64, powerpc, sh, m68k, & mips.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2008-08-12 22:09:06 +00:00
|
|
|
bool "Build targets in Documentation/ tree"
|
|
|
|
|
depends on HEADERS_CHECK
|
|
|
|
|
help
|
|
|
|
|
This option attempts to build objects from the source files in the
|
|
|
|
|
kernel Documentation/ tree.
|
|
|
|
|
|
|
|
|
|
Say N if you are unsure.
|
|
|
|
|
|
2009-02-05 16:51:38 +00:00
|
|
|
config DYNAMIC_DEBUG
|
2009-02-05 16:53:15 +00:00
|
|
|
bool "Enable dynamic printk() support"
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
default n
|
|
|
|
|
depends on PRINTK
|
2009-02-05 16:53:15 +00:00
|
|
|
depends on DEBUG_FS
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
help
|
|
|
|
|
|
|
|
|
|
Compiles debug level messages into the kernel, which would not
|
|
|
|
|
otherwise be available at runtime. These messages can then be
|
2009-02-05 16:53:15 +00:00
|
|
|
enabled/disabled based on various levels of scope - per source file,
|
|
|
|
|
function, module, format string, and line number. This mechanism
|
2012-04-27 20:30:41 +00:00
|
|
|
implicitly compiles in all pr_debug() and dev_dbg() calls, which
|
|
|
|
|
enlarges the kernel text size by about 2%.
|
|
|
|
|
|
|
|
|
|
If a source file is compiled with DEBUG flag set, any
|
|
|
|
|
pr_debug() calls in it are enabled by default, but can be
|
|
|
|
|
disabled at runtime as below. Note that DEBUG flag is
|
|
|
|
|
turned on by many CONFIG_*DEBUG* options.
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
|
|
|
|
Usage:
|
|
|
|
|
|
2010-05-24 21:33:21 +00:00
|
|
|
Dynamic debugging is controlled via the 'dynamic_debug/control' file,
|
2009-02-05 16:53:15 +00:00
|
|
|
which is contained in the 'debugfs' filesystem. Thus, the debugfs
|
|
|
|
|
filesystem must first be mounted before making use of this feature.
|
2010-05-24 21:33:21 +00:00
|
|
|
We refer the control file as: <debugfs>/dynamic_debug/control. This
|
2009-02-05 16:53:15 +00:00
|
|
|
file contains a list of the debug statements that can be enabled. The
|
|
|
|
|
format for each line of the file is:
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
filename:lineno [module]function flags format
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
filename : source file of the debug statement
|
|
|
|
|
lineno : line number of the debug statement
|
|
|
|
|
module : module that contains the debug statement
|
|
|
|
|
function : function that contains the debug statement
|
2012-04-27 20:30:41 +00:00
|
|
|
flags : '=p' means the line is turned 'on' for printing
|
2009-02-05 16:53:15 +00:00
|
|
|
format : the format used for the debug statement
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
|
|
|
|
From a live system:
|
|
|
|
|
|
2010-05-24 21:33:21 +00:00
|
|
|
nullarbor:~ # cat <debugfs>/dynamic_debug/control
|
2009-02-05 16:53:15 +00:00
|
|
|
# filename:lineno [module]function flags format
|
2012-04-27 20:30:41 +00:00
|
|
|
fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012"
|
|
|
|
|
fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012"
|
|
|
|
|
fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012"
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
Example usage:
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
// enable the message at line 1603 of file svcsock.c
|
|
|
|
|
nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
|
2010-05-24 21:33:21 +00:00
|
|
|
<debugfs>/dynamic_debug/control
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
// enable all the messages in file svcsock.c
|
|
|
|
|
nullarbor:~ # echo -n 'file svcsock.c +p' >
|
2010-05-24 21:33:21 +00:00
|
|
|
<debugfs>/dynamic_debug/control
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
// enable all the messages in the NFS server module
|
|
|
|
|
nullarbor:~ # echo -n 'module nfsd +p' >
|
2010-05-24 21:33:21 +00:00
|
|
|
<debugfs>/dynamic_debug/control
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
// enable all 12 messages in the function svc_process()
|
|
|
|
|
nullarbor:~ # echo -n 'func svc_process +p' >
|
2010-05-24 21:33:21 +00:00
|
|
|
<debugfs>/dynamic_debug/control
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
// disable all 12 messages in the function svc_process()
|
|
|
|
|
nullarbor:~ # echo -n 'func svc_process -p' >
|
2010-05-24 21:33:21 +00:00
|
|
|
<debugfs>/dynamic_debug/control
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-02-05 16:53:15 +00:00
|
|
|
See Documentation/dynamic-debug-howto.txt for additional information.
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2009-01-09 11:14:24 +00:00
|
|
|
config DMA_API_DEBUG
|
|
|
|
|
bool "Enable debugging of DMA-API usage"
|
|
|
|
|
depends on HAVE_DMA_API_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Enable this option to debug the use of the DMA API by device drivers.
|
|
|
|
|
With this option you will be able to detect common bugs in device
|
|
|
|
|
drivers like double-freeing of DMA mappings or freeing mappings that
|
|
|
|
|
were never allocated.
|
|
|
|
|
This option causes a performance degredation. Use only if you want
|
|
|
|
|
to debug device drivers. If unsure, say N.
|
driver core: basic infrastructure for per-module dynamic debug messages
Base infrastructure to enable per-module debug messages.
I've introduced CONFIG_DYNAMIC_PRINTK_DEBUG, which when enabled centralizes
control of debugging statements on a per-module basis in one /proc file,
currently, <debugfs>/dynamic_printk/modules. When, CONFIG_DYNAMIC_PRINTK_DEBUG,
is not set, debugging statements can still be enabled as before, often by
defining 'DEBUG' for the proper compilation unit. Thus, this patch set has no
affect when CONFIG_DYNAMIC_PRINTK_DEBUG is not set.
The infrastructure currently ties into all pr_debug() and dev_dbg() calls. That
is, if CONFIG_DYNAMIC_PRINTK_DEBUG is set, all pr_debug() and dev_dbg() calls
can be dynamically enabled/disabled on a per-module basis.
Future plans include extending this functionality to subsystems, that define
their own debug levels and flags.
Usage:
Dynamic debugging is controlled by the debugfs file,
<debugfs>/dynamic_printk/modules. This file contains a list of the modules that
can be enabled. The format of the file is as follows:
<module_name> <enabled=0/1>
.
.
.
<module_name> : Name of the module in which the debug call resides
<enabled=0/1> : whether the messages are enabled or not
For example:
snd_hda_intel enabled=0
fixup enabled=1
driver enabled=0
Enable a module:
$echo "set enabled=1 <module_name>" > dynamic_printk/modules
Disable a module:
$echo "set enabled=0 <module_name>" > dynamic_printk/modules
Enable all modules:
$echo "set enabled=1 all" > dynamic_printk/modules
Disable all modules:
$echo "set enabled=0 all" > dynamic_printk/modules
Finally, passing "dynamic_printk" at the command line enables
debugging for all modules. This mode can be turned off via the above
disable command.
[gkh: minor cleanups and tweaks to make the build work quietly]
Signed-off-by: Jason Baron <jbaron@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2008-08-12 20:46:19 +00:00
|
|
|
|
2010-02-24 09:54:24 +00:00
|
|
|
config ATOMIC64_SELFTEST
|
|
|
|
|
bool "Perform an atomic64_t self-test at boot"
|
|
|
|
|
help
|
|
|
|
|
Enable this option to test the atomic64_t functions at boot.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-10-07 22:25:04 +00:00
|
|
|
config ASYNC_RAID6_TEST
|
|
|
|
|
tristate "Self test for hardware accelerated raid6 recovery"
|
|
|
|
|
depends on ASYNC_RAID6_RECOV
|
|
|
|
|
select ASYNC_MEMCPY
|
|
|
|
|
---help---
|
|
|
|
|
This is a one-shot self test that permutes through the
|
|
|
|
|
recovery of all the possible two disk failure scenarios for a
|
|
|
|
|
N-disk array. Recovery is performed with the asynchronous
|
|
|
|
|
raid6 recovery routines, and will optionally use an offload
|
|
|
|
|
engine if one is available.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-10-19 06:41:07 +00:00
|
|
|
source "samples/Kconfig"
|
2008-04-17 18:05:37 +00:00
|
|
|
|
|
|
|
|
source "lib/Kconfig.kgdb"
|
2009-02-26 19:38:56 +00:00
|
|
|
|
|
|
|
|
source "lib/Kconfig.kmemcheck"
|
2011-03-22 23:34:40 +00:00
|
|
|
|
2013-04-30 22:27:30 +00:00
|
|
|
config TEST_STRING_HELPERS
|
|
|
|
|
tristate "Test functions located in the string_helpers module at runtime"
|
|
|
|
|
|
2011-03-22 23:34:40 +00:00
|
|
|
config TEST_KSTRTOX
|
|
|
|
|
tristate "Test kstrto*() family of functions at runtime"
|