Lines Matching refs:kernel
15 The behavior is also controlled by the kernel command line
16 parameter printk.time=1. See Documentation/kernel-parameters.txt
33 This build option allows you to read kernel boot messages
35 specified in milliseconds on the kernel command line,
54 Compiles debug level messages into the kernel, which would not
59 enlarges the kernel text size by about 2%.
121 bool "Compile the kernel with debug info"
124 If you say Y here the resulting kernel image will include
125 debugging info resulting in a larger kernel image.
126 This adds debug symbols to the kernel and modules (gcc -g), and
127 is needed if you intend to use kernel crashdump or binary object
128 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
129 Say Y here only if you plan to debug the kernel.
171 bool "Provide GDB scripts for kernel debugging"
177 additional functions are available to analyze a Linux kernel
178 instance. See Documentation/gdb-kernel-debugging.txt for further
185 Enable the __deprecated logic in the kernel build.
187 (declared at kernel/power/somefile.c:1234)" messages.
193 Enable the __must_check logic in the kernel build. Disable this to
222 assembler output. This may make the kernel slightly slower, but it helps
223 to keep kernel developers who have to stare a lot at assembler listings
230 Unused but exported symbols make the kernel needlessly bigger. For
233 some external kernel module needs one of these symbols anyway. If you
235 using the right API. (rationale: since nobody in the kernel is using
238 mail to the linux kernel mailing list mentioning the symbol and why
239 you really need it, and what the merge plan to the mainline kernel for
261 debugfs is a virtual file system that kernel developers use to put
274 This option will extract the user-visible kernel headers whenever
275 building the kernel, and will run basic sanity checks on them to
296 kernel build, and enabling this option causes the following
303 a larger kernel).
334 bool "Compile the kernel with frame pointers"
341 If you say Y here the resulting kernel image will be slightly
343 in case of kernel bugs. (precise oopses/stacktraces/warnings)
367 if the system crashes for example during kernel debugging (e.g., you
389 identify kernel problems.
400 kernel to track the life time of various objects and validate
460 Say Y here to have the kernel do limited verification on memory
478 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
509 only shown in /sys/kernel/debug/kmemleak. Enabling this
518 mounted (usually at /sys/kernel/debug).
533 tristate "Simple test for the kernel memory leak detector"
617 debugfs interface under /sys/kernel/debug/notifier-error-inject/memory
624 # cd /sys/kernel/debug/notifier-error-inject/memory
640 been set up. This adds a fair amount of code to kernel memory
659 Say Y here if you want to check for overflows of kernel, IRQ
665 kernel get too deep, especially when interrupts are
694 Say Y here to enable the kernel to act as a watchdog to detect
697 Softlockups are bugs that cause the kernel to loop in kernel
702 Hardlockups are bugs that cause the CPU to loop in kernel mode
723 Say Y here to enable the kernel to panic on "hard lockups",
724 which are bugs that cause the kernel to loop in kernel
741 Say Y here to enable the kernel to panic on "soft lockups",
742 which are bugs that cause the kernel to loop in kernel
766 Say Y here to enable the kernel to detect "hung tasks",
770 When a hung task is detected, the kernel will print the
785 It can be adjusted at runtime via the kernel.hung_task_timeout_secs
787 /proc/sys/kernel/hung_task_timeout_secs.
796 Say Y here to enable the kernel to panic on "hung tasks",
797 which are bugs that cause the kernel to leave a task stuck
820 Say Y here to enable the kernel to panic when it oopses. This
821 has the same effect as setting oops=panic on the kernel command
824 This feature is useful to ensure that the kernel does not do
841 the kernel panics. If n = 0, then we wait forever. A timeout
897 bool "Collect kernel timers statistics"
901 timer routines to collect statistics about kernel timers being
905 about timer usage patterns in kernel and userspace. This feature
906 is lightweight if enabled in the kernel config but not activated
911 bool "Debug preemptible kernel"
915 If you say Y here then the kernel will use a debug variant of the
917 if kernel code uses it in a preemption-unsafe way. Also, the kernel
959 it really should not be enabled in a production or distro kernel,
960 even a debug kernel. If you are a driver writer, enable it. If
971 mutex or rwsem) is incorrectly freed by the kernel, via any of the
987 This feature enables the kernel to prove that all locking
988 that occurs in the kernel runtime is mathematically
995 In short, this feature enables the kernel to report locking
1005 reported by the kernel (once the event is observed that
1009 observed by the kernel, are mathematically correct), the
1010 kernel reports nothing.
1071 Say Y here if you want the kernel to run a short self-test during
1084 This option provides a kernel module that runs torture tests
1085 on kernel locking primitives. The kernel module may be built
1086 after the fact on the running kernel to be tested, if desired.
1088 Say Y here if you want kernel locking-primitive torture tests
1089 to be built into the kernel.
1105 This option causes the kernel to create a /proc/pid/stack for
1107 It is also used by various kernel debugging features that require
1132 If you say Y here, the kernel will delay the release of kobjects
1182 This is most useful for kernel developers to make sure that
1248 This option provides a kernel module that runs torture tests
1249 on the RCU infrastructure. The kernel module may be built
1250 after the fact on the running kernel to be tested, if desired.
1253 the kernel.
1263 directly into the kernel without them starting up at boot
1264 time. You can use /proc/sys/kernel/rcutorture_runnable
1267 into the kernel.
1283 makes your kernel less stable. It can also greatly increase
1308 kernel less stable. It can also greatly increase grace-period
1332 cleanup, in other words, it makes your kernel less stable.
1379 Say N here if you need ultimate kernel/user switch latencies
1399 the extended space and spreads them to discover kernel or
1426 This option provides a kernel module that can be used to test
1429 debugfs interface under /sys/kernel/debug/notifier-error-inject/cpu
1436 # cd /sys/kernel/debug/notifier-error-inject/cpu
1453 interface /sys/kernel/debug/notifier-error-inject/pm
1460 # cd /sys/kernel/debug/notifier-error-inject/pm/
1477 /sys/kernel/debug/notifier-error-inject/OF-reconfig/
1571 to find out which userspace is blocking on what kernel operations.
1591 source kernel/trace/Kconfig
1636 This option provides a kernel module that can be used to test
1637 the kernel stack backtrace code. This option is not useful
1638 for distributions or general kernels, but only for kernel
1715 If you want to debug problems which hang or crash the kernel early
1723 Even controlling a kernel debugger is possible using remote DMA.
1745 kernel Documentation/ tree.
1783 tristate "Test user/kernel boundary protections"
1789 user/kernel boundary testing is working. If it fails to load,
1790 a regression has been detected in the user/kernel memory boundary
1835 This option adds a kernel parameter 'memtest', which allows memtest