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
221 assembler output. This may make the kernel slightly slower, but it helps
222 to keep kernel developers who have to stare a lot at assembler listings
229 Unused but exported symbols make the kernel needlessly bigger. For
232 some external kernel module needs one of these symbols anyway. If you
234 using the right API. (rationale: since nobody in the kernel is using
237 mail to the linux kernel mailing list mentioning the symbol and why
238 you really need it, and what the merge plan to the mainline kernel for
260 debugfs is a virtual file system that kernel developers use to put
273 This option will extract the user-visible kernel headers whenever
274 building the kernel, and will run basic sanity checks on them to
295 kernel build, and enabling this option causes the following
302 a larger kernel).
324 bool "Compile the kernel with frame pointers"
331 If you say Y here the resulting kernel image will be slightly
333 in case of kernel bugs. (precise oopses/stacktraces/warnings)
357 if the system crashes for example during kernel debugging (e.g., you
379 identify kernel problems.
390 kernel to track the life time of various objects and validate
450 Say Y here to have the kernel do limited verification on memory
468 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
499 only shown in /sys/kernel/debug/kmemleak. Enabling this
508 mounted (usually at /sys/kernel/debug).
523 tristate "Simple test for the kernel memory leak detector"
607 debugfs interface under /sys/kernel/debug/notifier-error-inject/memory
614 # cd /sys/kernel/debug/notifier-error-inject/memory
630 been set up. This adds a fair amount of code to kernel memory
649 Say Y here if you want to check for overflows of kernel, IRQ
655 kernel get too deep, especially when interrupts are
684 Say Y here to enable the kernel to act as a watchdog to detect
687 Softlockups are bugs that cause the kernel to loop in kernel
692 Hardlockups are bugs that cause the CPU to loop in kernel mode
713 Say Y here to enable the kernel to panic on "hard lockups",
714 which are bugs that cause the kernel to loop in kernel
731 Say Y here to enable the kernel to panic on "soft lockups",
732 which are bugs that cause the kernel to loop in kernel
756 Say Y here to enable the kernel to detect "hung tasks",
760 When a hung task is detected, the kernel will print the
775 It can be adjusted at runtime via the kernel.hung_task_timeout_secs
777 /proc/sys/kernel/hung_task_timeout_secs.
786 Say Y here to enable the kernel to panic on "hung tasks",
787 which are bugs that cause the kernel to leave a task stuck
810 Say Y here to enable the kernel to panic when it oopses. This
811 has the same effect as setting oops=panic on the kernel command
814 This feature is useful to ensure that the kernel does not do
831 the kernel panics. If n = 0, then we wait forever. A timeout
882 bool "Collect kernel timers statistics"
886 timer routines to collect statistics about kernel timers being
890 about timer usage patterns in kernel and userspace. This feature
891 is lightweight if enabled in the kernel config but not activated
896 bool "Debug preemptible kernel"
900 If you say Y here then the kernel will use a debug variant of the
902 if kernel code uses it in a preemption-unsafe way. Also, the kernel
950 it really should not be enabled in a production or distro kernel,
951 even a debug kernel. If you are a driver writer, enable it. If
962 mutex or rwsem) is incorrectly freed by the kernel, via any of the
978 This feature enables the kernel to prove that all locking
979 that occurs in the kernel runtime is mathematically
986 In short, this feature enables the kernel to report locking
996 reported by the kernel (once the event is observed that
1000 observed by the kernel, are mathematically correct), the
1001 kernel reports nothing.
1062 Say Y here if you want the kernel to run a short self-test during
1075 This option provides a kernel module that runs torture tests
1076 on kernel locking primitives. The kernel module may be built
1077 after the fact on the running kernel to be tested, if desired.
1079 Say Y here if you want kernel locking-primitive torture tests
1080 to be built into the kernel.
1096 This option causes the kernel to create a /proc/pid/stack for
1098 It is also used by various kernel debugging features that require
1123 If you say Y here, the kernel will delay the release of kobjects
1173 This is most useful for kernel developers to make sure that
1238 This option provides a kernel module that runs torture tests
1239 on the RCU infrastructure. The kernel module may be built
1240 after the fact on the running kernel to be tested, if desired.
1243 the kernel.
1253 directly into the kernel without them starting up at boot
1254 time. You can use /proc/sys/kernel/rcutorture_runnable
1257 into the kernel.
1272 kernel less stable. It can also greatly increase grace-period
1342 the extended space and spreads them to discover kernel or
1369 This option provides a kernel module that can be used to test
1372 debugfs interface under /sys/kernel/debug/notifier-error-inject/cpu
1379 # cd /sys/kernel/debug/notifier-error-inject/cpu
1396 interface /sys/kernel/debug/notifier-error-inject/pm
1403 # cd /sys/kernel/debug/notifier-error-inject/pm/
1420 /sys/kernel/debug/notifier-error-inject/OF-reconfig/
1507 to find out which userspace is blocking on what kernel operations.
1527 source kernel/trace/Kconfig
1572 This option provides a kernel module that can be used to test
1573 the kernel stack backtrace code. This option is not useful
1574 for distributions or general kernels, but only for kernel
1648 If you want to debug problems which hang or crash the kernel early
1656 Even controlling a kernel debugger is possible using remote DMA.
1678 kernel Documentation/ tree.
1716 tristate "Test user/kernel boundary protections"
1722 user/kernel boundary testing is working. If it fails to load,
1723 a regression has been detected in the user/kernel memory boundary
1768 This option adds a kernel parameter 'memtest', which allows memtest