1 # SPDX-License-Identifier: GPL-2.0-only
4 menu "printk and dmesg options"
7 bool "Show timing information on printks"
10 Selecting this option causes time stamps of the printk()
11 messages to be added to the output of the syslog() system
12 call and at the console.
14 The timestamp is always recorded internally, and exported
15 to /dev/kmsg. This flag just specifies if the timestamp should
16 be included, not that the timestamp is recorded.
18 The behavior is also controlled by the kernel command line
19 parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst
22 bool "Show caller information on printks"
25 Selecting this option causes printk() to add a caller "thread id" (if
26 in task context) or a caller "processor id" (if not in task context)
29 This option is intended for environments where multiple threads
30 concurrently call printk() for many times, for it is difficult to
31 interpret without knowing where these lines (or sometimes individual
32 line which was divided into multiple lines due to race) came from.
34 Since toggling after boot makes the code racy, currently there is
35 no option to enable/disable at the kernel command line parameter or
38 config CONSOLE_LOGLEVEL_DEFAULT
39 int "Default console loglevel (1-15)"
43 Default loglevel to determine what will be printed on the console.
45 Setting a default here is equivalent to passing in loglevel=<x> in
46 the kernel bootargs. loglevel=<x> continues to override whatever
47 value is specified here as well.
49 Note: This does not affect the log level of un-prefixed printk()
50 usage in the kernel. That is controlled by the MESSAGE_LOGLEVEL_DEFAULT
53 config CONSOLE_LOGLEVEL_QUIET
54 int "quiet console loglevel (1-15)"
58 loglevel to use when "quiet" is passed on the kernel commandline.
60 When "quiet" is passed on the kernel commandline this loglevel
61 will be used as the loglevel. IOW passing "quiet" will be the
62 equivalent of passing "loglevel=<CONSOLE_LOGLEVEL_QUIET>"
64 config MESSAGE_LOGLEVEL_DEFAULT
65 int "Default message log level (1-7)"
69 Default log level for printk statements with no specified priority.
71 This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
72 that are auditing their logs closely may want to set it to a lower
75 Note: This does not affect what message level gets printed on the console
76 by default. To change that, use loglevel=<x> in the kernel bootargs,
77 or pick a different CONSOLE_LOGLEVEL_DEFAULT configuration value.
79 config BOOT_PRINTK_DELAY
80 bool "Delay each boot printk message by N milliseconds"
81 depends on DEBUG_KERNEL && PRINTK && GENERIC_CALIBRATE_DELAY
83 This build option allows you to read kernel boot messages
84 by inserting a short delay after each one. The delay is
85 specified in milliseconds on the kernel command line,
88 It is likely that you would also need to use "lpj=M" to preset
89 the "loops per jiffie" value.
90 See a previous boot log for the "lpj" value to use for your
91 system, and then set "lpj=M" before setting "boot_delay=N".
92 NOTE: Using this option may adversely affect SMP systems.
93 I.e., processors other than the first one may not boot up.
94 BOOT_PRINTK_DELAY also may cause LOCKUP_DETECTOR to detect
95 what it believes to be lockup conditions.
98 bool "Enable dynamic printk() support"
101 depends on (DEBUG_FS || PROC_FS)
102 select DYNAMIC_DEBUG_CORE
105 Compiles debug level messages into the kernel, which would not
106 otherwise be available at runtime. These messages can then be
107 enabled/disabled based on various levels of scope - per source file,
108 function, module, format string, and line number. This mechanism
109 implicitly compiles in all pr_debug() and dev_dbg() calls, which
110 enlarges the kernel text size by about 2%.
112 If a source file is compiled with DEBUG flag set, any
113 pr_debug() calls in it are enabled by default, but can be
114 disabled at runtime as below. Note that DEBUG flag is
115 turned on by many CONFIG_*DEBUG* options.
119 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
120 which is contained in the 'debugfs' filesystem or procfs.
121 Thus, the debugfs or procfs filesystem must first be mounted before
122 making use of this feature.
123 We refer the control file as: <debugfs>/dynamic_debug/control. This
124 file contains a list of the debug statements that can be enabled. The
125 format for each line of the file is:
127 filename:lineno [module]function flags format
129 filename : source file of the debug statement
130 lineno : line number of the debug statement
131 module : module that contains the debug statement
132 function : function that contains the debug statement
133 flags : '=p' means the line is turned 'on' for printing
134 format : the format used for the debug statement
138 nullarbor:~ # cat <debugfs>/dynamic_debug/control
139 # filename:lineno [module]function flags format
140 fs/aio.c:222 [aio]__put_ioctx =_ "__put_ioctx:\040freeing\040%p\012"
141 fs/aio.c:248 [aio]ioctx_alloc =_ "ENOMEM:\040nr_events\040too\040high\012"
142 fs/aio.c:1770 [aio]sys_io_cancel =_ "calling\040cancel\012"
146 // enable the message at line 1603 of file svcsock.c
147 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
148 <debugfs>/dynamic_debug/control
150 // enable all the messages in file svcsock.c
151 nullarbor:~ # echo -n 'file svcsock.c +p' >
152 <debugfs>/dynamic_debug/control
154 // enable all the messages in the NFS server module
155 nullarbor:~ # echo -n 'module nfsd +p' >
156 <debugfs>/dynamic_debug/control
158 // enable all 12 messages in the function svc_process()
159 nullarbor:~ # echo -n 'func svc_process +p' >
160 <debugfs>/dynamic_debug/control
162 // disable all 12 messages in the function svc_process()
163 nullarbor:~ # echo -n 'func svc_process -p' >
164 <debugfs>/dynamic_debug/control
166 See Documentation/admin-guide/dynamic-debug-howto.rst for additional
169 config DYNAMIC_DEBUG_CORE
170 bool "Enable core function of dynamic debug support"
172 depends on (DEBUG_FS || PROC_FS)
174 Enable core functional support of dynamic debug. It is useful
175 when you want to tie dynamic debug to your kernel modules with
176 DYNAMIC_DEBUG_MODULE defined for each of them, especially for
177 the case of embedded system where the kernel image size is
178 sensitive for people.
180 config SYMBOLIC_ERRNAME
181 bool "Support symbolic error names in printf"
184 If you say Y here, the kernel's printf implementation will
185 be able to print symbolic error names such as ENOSPC instead
186 of the number 28. It makes the kernel image slightly larger
187 (about 3KB), but can make the kernel logs easier to read.
189 config DEBUG_BUGVERBOSE
190 bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT
191 depends on BUG && (GENERIC_BUG || HAVE_DEBUG_BUGVERBOSE)
194 Say Y here to make BUG() panics output the file name and line number
195 of the BUG call as well as the EIP and oops trace. This aids
196 debugging but costs about 70-100K of memory.
198 endmenu # "printk and dmesg options"
200 menu "Compile-time checks and compiler options"
203 bool "Compile the kernel with debug info"
204 depends on DEBUG_KERNEL && !COMPILE_TEST
206 If you say Y here the resulting kernel image will include
207 debugging info resulting in a larger kernel image.
208 This adds debug symbols to the kernel and modules (gcc -g), and
209 is needed if you intend to use kernel crashdump or binary object
210 tools like crash, kgdb, LKCD, gdb, etc on the kernel.
211 Say Y here only if you plan to debug the kernel.
217 config DEBUG_INFO_REDUCED
218 bool "Reduce debugging information"
220 If you say Y here gcc is instructed to generate less debugging
221 information for structure types. This means that tools that
222 need full debugging information (like kgdb or systemtap) won't
223 be happy. But if you merely need debugging information to
224 resolve line numbers there is no loss. Advantage is that
225 build directory object sizes shrink dramatically over a full
226 DEBUG_INFO build and compile times are reduced too.
227 Only works with newer gcc versions.
229 config DEBUG_INFO_COMPRESSED
230 bool "Compressed debugging information"
231 depends on $(cc-option,-gz=zlib)
232 depends on $(ld-option,--compress-debug-sections=zlib)
234 Compress the debug information using zlib. Requires GCC 5.0+ or Clang
235 5.0+, binutils 2.26+, and zlib.
237 Users of dpkg-deb via scripts/package/builddeb may find an increase in
238 size of their debug .deb packages with this config set, due to the
239 debug info being compressed with zlib, then the object files being
240 recompressed with a different compression scheme. But this is still
241 preferable to setting $KDEB_COMPRESS to "none" which would be even
244 config DEBUG_INFO_SPLIT
245 bool "Produce split debuginfo in .dwo files"
246 depends on $(cc-option,-gsplit-dwarf)
248 Generate debug info into separate .dwo files. This significantly
249 reduces the build directory size for builds with DEBUG_INFO,
250 because it stores the information only once on disk in .dwo
251 files instead of multiple times in object files and executables.
252 In addition the debug information is also compressed.
254 Requires recent gcc (4.7+) and recent gdb/binutils.
255 Any tool that packages or reads debug information would need
256 to know about the .dwo files and include them.
257 Incompatible with older versions of ccache.
260 prompt "DWARF version"
262 Which version of DWARF debug info to emit.
264 config DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT
265 bool "Rely on the toolchain's implicit default DWARF version"
267 The implicit default version of DWARF debug info produced by a
268 toolchain changes over time.
270 This can break consumers of the debug info that haven't upgraded to
271 support newer revisions, and prevent testing newer versions, but
272 those should be less common scenarios.
276 config DEBUG_INFO_DWARF4
277 bool "Generate DWARF Version 4 debuginfo"
279 Generate DWARF v4 debug info. This requires gcc 4.5+ and gdb 7.0+.
281 If you have consumers of DWARF debug info that are not ready for
282 newer revisions of DWARF, you may wish to choose this or have your
285 config DEBUG_INFO_DWARF5
286 bool "Generate DWARF Version 5 debuginfo"
287 depends on GCC_VERSION >= 50000 || (CC_IS_CLANG && (AS_IS_LLVM || (AS_IS_GNU && AS_VERSION >= 23502)))
288 depends on !DEBUG_INFO_BTF
290 Generate DWARF v5 debug info. Requires binutils 2.35.2, gcc 5.0+ (gcc
291 5.0+ accepts the -gdwarf-5 flag but only had partial support for some
292 draft features until 7.0), and gdb 8.0+.
294 Changes to the structure of debug info in Version 5 allow for around
295 15-18% savings in resulting image and debug info section sizes as
296 compared to DWARF Version 4. DWARF Version 5 standardizes previous
297 extensions such as accelerators for symbol indexing and the format
298 for fission (.dwo/.dwp) files. Users may not want to select this
299 config if they rely on tooling that has not yet been updated to
300 support DWARF Version 5.
302 endchoice # "DWARF version"
304 config DEBUG_INFO_BTF
305 bool "Generate BTF typeinfo"
306 depends on !DEBUG_INFO_SPLIT && !DEBUG_INFO_REDUCED
307 depends on !GCC_PLUGIN_RANDSTRUCT || COMPILE_TEST
309 Generate deduplicated BTF type information from DWARF debug info.
310 Turning this on expects presence of pahole tool, which will convert
311 DWARF type info into equivalent deduplicated BTF type info.
313 config PAHOLE_HAS_SPLIT_BTF
314 def_bool $(success, test `$(PAHOLE) --version | sed -E 's/v([0-9]+)\.([0-9]+)/\1\2/'` -ge "119")
316 config DEBUG_INFO_BTF_MODULES
318 depends on DEBUG_INFO_BTF && MODULES && PAHOLE_HAS_SPLIT_BTF
320 Generate compact split BTF type information for kernel modules.
323 bool "Provide GDB scripts for kernel debugging"
325 This creates the required links to GDB helper scripts in the
326 build directory. If you load vmlinux into gdb, the helper
327 scripts will be automatically imported by gdb as well, and
328 additional functions are available to analyze a Linux kernel
329 instance. See Documentation/dev-tools/gdb-kernel-debugging.rst
335 int "Warn for stack frames larger than"
337 default 2048 if GCC_PLUGIN_LATENT_ENTROPY
338 default 1280 if (!64BIT && PARISC)
339 default 1024 if (!64BIT && !PARISC)
340 default 2048 if 64BIT
342 Tell gcc to warn at build time for stack frames larger than this.
343 Setting this too low will cause a lot of warnings.
344 Setting it to 0 disables the warning.
346 config STRIP_ASM_SYMS
347 bool "Strip assembler-generated symbols during link"
350 Strip internal assembler-generated symbols during a link (symbols
351 that look like '.Lxxx') so they don't pollute the output of
352 get_wchan() and suchlike.
355 bool "Generate readable assembler code"
356 depends on DEBUG_KERNEL
358 Disable some compiler optimizations that tend to generate human unreadable
359 assembler output. This may make the kernel slightly slower, but it helps
360 to keep kernel developers who have to stare a lot at assembler listings
363 config HEADERS_INSTALL
364 bool "Install uapi headers to usr/include"
367 This option will install uapi headers (headers exported to user-space)
368 into the usr/include directory for use during the kernel build.
369 This is unneeded for building the kernel itself, but needed for some
370 user-space program samples. It is also needed by some features such
371 as uapi header sanity checks.
373 config DEBUG_SECTION_MISMATCH
374 bool "Enable full Section mismatch analysis"
376 The section mismatch analysis checks if there are illegal
377 references from one section to another section.
378 During linktime or runtime, some sections are dropped;
379 any use of code/data previously in these sections would
380 most likely result in an oops.
381 In the code, functions and variables are annotated with
382 __init,, etc. (see the full list in include/linux/init.h),
383 which results in the code/data being placed in specific sections.
384 The section mismatch analysis is always performed after a full
385 kernel build, and enabling this option causes the following
386 additional step to occur:
387 - Add the option -fno-inline-functions-called-once to gcc commands.
388 When inlining a function annotated with __init in a non-init
389 function, we would lose the section information and thus
390 the analysis would not catch the illegal reference.
391 This option tells gcc to inline less (but it does result in
394 config SECTION_MISMATCH_WARN_ONLY
395 bool "Make section mismatch errors non-fatal"
398 If you say N here, the build process will fail if there are any
399 section mismatch, instead of just throwing warnings.
403 config DEBUG_FORCE_FUNCTION_ALIGN_32B
404 bool "Force all function address 32B aligned" if EXPERT
406 There are cases that a commit from one domain changes the function
407 address alignment of other domains, and cause magic performance
408 bump (regression or improvement). Enable this option will help to
409 verify if the bump is caused by function alignment changes, while
410 it will slightly increase the kernel size and affect icache usage.
412 It is mainly for debug and performance tuning use.
415 # Select this config option from the architecture Kconfig, if it
416 # is preferred to always offer frame pointers as a config
417 # option on the architecture (regardless of KERNEL_DEBUG):
419 config ARCH_WANT_FRAME_POINTERS
423 bool "Compile the kernel with frame pointers"
424 depends on DEBUG_KERNEL && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS
425 default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS
427 If you say Y here the resulting kernel image will be slightly
428 larger and slower, but it gives very useful debugging information
429 in case of kernel bugs. (precise oopses/stacktraces/warnings)
431 config STACK_VALIDATION
432 bool "Compile-time stack metadata validation"
433 depends on HAVE_STACK_VALIDATION
436 Add compile-time checks to validate stack metadata, including frame
437 pointers (if CONFIG_FRAME_POINTER is enabled). This helps ensure
438 that runtime stack traces are more reliable.
440 This is also a prerequisite for generation of ORC unwind data, which
441 is needed for CONFIG_UNWINDER_ORC.
443 For more information, see
444 tools/objtool/Documentation/stack-validation.txt.
446 config VMLINUX_VALIDATION
448 depends on STACK_VALIDATION && DEBUG_ENTRY && !PARAVIRT
452 bool "Generate vmlinux.map file when linking"
455 Selecting this option will pass "-Map=vmlinux.map" to ld
456 when linking vmlinux. That file can be useful for verifying
457 and debugging magic section games, and for seeing which
458 pieces of code get eliminated with
459 CONFIG_LD_DEAD_CODE_DATA_ELIMINATION.
461 config DEBUG_FORCE_WEAK_PER_CPU
462 bool "Force weak per-cpu definitions"
463 depends on DEBUG_KERNEL
465 s390 and alpha require percpu variables in modules to be
466 defined weak to work around addressing range issue which
467 puts the following two restrictions on percpu variable
470 1. percpu symbols must be unique whether static or not
471 2. percpu variables can't be defined inside a function
473 To ensure that generic code follows the above rules, this
474 option forces all percpu variables to be defined as weak.
476 endmenu # "Compiler options"
478 menu "Generic Kernel Debugging Instruments"
481 bool "Magic SysRq key"
484 If you say Y here, you will have some control over the system even
485 if the system crashes for example during kernel debugging (e.g., you
486 will be able to flush the buffer cache to disk, reboot the system
487 immediately or dump some status information). This is accomplished
488 by pressing various keys while holding SysRq (Alt+PrintScreen). It
489 also works on a serial console (on PC hardware at least), if you
490 send a BREAK and then within 5 seconds a command keypress. The
491 keys are documented in <file:Documentation/admin-guide/sysrq.rst>.
492 Don't say Y unless you really know what this hack does.
494 config MAGIC_SYSRQ_DEFAULT_ENABLE
495 hex "Enable magic SysRq key functions by default"
496 depends on MAGIC_SYSRQ
499 Specifies which SysRq key functions are enabled by default.
500 This may be set to 1 or 0 to enable or disable them all, or
501 to a bitmask as described in Documentation/admin-guide/sysrq.rst.
503 config MAGIC_SYSRQ_SERIAL
504 bool "Enable magic SysRq key over serial"
505 depends on MAGIC_SYSRQ
508 Many embedded boards have a disconnected TTL level serial which can
509 generate some garbage that can lead to spurious false sysrq detects.
510 This option allows you to decide whether you want to enable the
513 config MAGIC_SYSRQ_SERIAL_SEQUENCE
514 string "Char sequence that enables magic SysRq over serial"
515 depends on MAGIC_SYSRQ_SERIAL
518 Specifies a sequence of characters that can follow BREAK to enable
519 SysRq on a serial console.
521 If unsure, leave an empty string and the option will not be enabled.
524 bool "Debug Filesystem"
526 debugfs is a virtual file system that kernel developers use to put
527 debugging files into. Enable this option to be able to read and
528 write to these files.
530 For detailed documentation on the debugfs API, see
531 Documentation/filesystems/.
536 prompt "Debugfs default access"
538 default DEBUG_FS_ALLOW_ALL
540 This selects the default access restrictions for debugfs.
541 It can be overridden with kernel command line option
542 debugfs=[on,no-mount,off]. The restrictions apply for API access
543 and filesystem registration.
545 config DEBUG_FS_ALLOW_ALL
548 No restrictions apply. Both API and filesystem registration
549 is on. This is the normal default operation.
551 config DEBUG_FS_DISALLOW_MOUNT
552 bool "Do not register debugfs as filesystem"
554 The API is open but filesystem is not loaded. Clients can still do
555 their work and read with debug tools that do not need
558 config DEBUG_FS_ALLOW_NONE
561 Access is off. Clients get -PERM when trying to create nodes in
562 debugfs tree and debugfs is not registered as a filesystem.
563 Client can then back-off or continue without debugfs access.
567 source "lib/Kconfig.kgdb"
568 source "lib/Kconfig.ubsan"
569 source "lib/Kconfig.kcsan"
574 bool "Kernel debugging"
576 Say Y here if you are developing drivers or trying to debug and
577 identify kernel problems.
580 bool "Miscellaneous debug code"
582 depends on DEBUG_KERNEL
584 Say Y here if you need to enable miscellaneous debug code that should
585 be under a more specific debug option but isn't.
588 menu "Memory Debugging"
590 source "mm/Kconfig.debug"
593 bool "Debug object operations"
594 depends on DEBUG_KERNEL
596 If you say Y here, additional code will be inserted into the
597 kernel to track the life time of various objects and validate
598 the operations on those objects.
600 config DEBUG_OBJECTS_SELFTEST
601 bool "Debug objects selftest"
602 depends on DEBUG_OBJECTS
604 This enables the selftest of the object debug code.
606 config DEBUG_OBJECTS_FREE
607 bool "Debug objects in freed memory"
608 depends on DEBUG_OBJECTS
610 This enables checks whether a k/v free operation frees an area
611 which contains an object which has not been deactivated
612 properly. This can make kmalloc/kfree-intensive workloads
615 config DEBUG_OBJECTS_TIMERS
616 bool "Debug timer objects"
617 depends on DEBUG_OBJECTS
619 If you say Y here, additional code will be inserted into the
620 timer routines to track the life time of timer objects and
621 validate the timer operations.
623 config DEBUG_OBJECTS_WORK
624 bool "Debug work objects"
625 depends on DEBUG_OBJECTS
627 If you say Y here, additional code will be inserted into the
628 work queue routines to track the life time of work objects and
629 validate the work operations.
631 config DEBUG_OBJECTS_RCU_HEAD
632 bool "Debug RCU callbacks objects"
633 depends on DEBUG_OBJECTS
635 Enable this to turn on debugging of RCU list heads (call_rcu() usage).
637 config DEBUG_OBJECTS_PERCPU_COUNTER
638 bool "Debug percpu counter objects"
639 depends on DEBUG_OBJECTS
641 If you say Y here, additional code will be inserted into the
642 percpu counter routines to track the life time of percpu counter
643 objects and validate the percpu counter operations.
645 config DEBUG_OBJECTS_ENABLE_DEFAULT
646 int "debug_objects bootup default value (0-1)"
649 depends on DEBUG_OBJECTS
651 Debug objects boot parameter default value
654 bool "Debug slab memory allocations"
655 depends on DEBUG_KERNEL && SLAB
657 Say Y here to have the kernel do limited verification on memory
658 allocation as well as poisoning memory on free to catch use of freed
659 memory. This can make kmalloc/kfree-intensive workloads much slower.
662 bool "SLUB debugging on by default"
663 depends on SLUB && SLUB_DEBUG
666 Boot with debugging on by default. SLUB boots by default with
667 the runtime debug capabilities switched off. Enabling this is
668 equivalent to specifying the "slub_debug" parameter on boot.
669 There is no support for more fine grained debug control like
670 possible with slub_debug=xxx. SLUB debugging may be switched
671 off in a kernel built with CONFIG_SLUB_DEBUG_ON by specifying
676 bool "Enable SLUB performance statistics"
677 depends on SLUB && SYSFS
679 SLUB statistics are useful to debug SLUBs allocation behavior in
680 order find ways to optimize the allocator. This should never be
681 enabled for production use since keeping statistics slows down
682 the allocator by a few percentage points. The slabinfo command
683 supports the determination of the most active slabs to figure
684 out which slabs are relevant to a particular load.
685 Try running: slabinfo -DA
687 config HAVE_DEBUG_KMEMLEAK
690 config DEBUG_KMEMLEAK
691 bool "Kernel memory leak detector"
692 depends on DEBUG_KERNEL && HAVE_DEBUG_KMEMLEAK
694 select STACKTRACE if STACKTRACE_SUPPORT
698 Say Y here if you want to enable the memory leak
699 detector. The memory allocation/freeing is traced in a way
700 similar to the Boehm's conservative garbage collector, the
701 difference being that the orphan objects are not freed but
702 only shown in /sys/kernel/debug/kmemleak. Enabling this
703 feature will introduce an overhead to memory
704 allocations. See Documentation/dev-tools/kmemleak.rst for more
707 Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances
708 of finding leaks due to the slab objects poisoning.
710 In order to access the kmemleak file, debugfs needs to be
711 mounted (usually at /sys/kernel/debug).
713 config DEBUG_KMEMLEAK_MEM_POOL_SIZE
714 int "Kmemleak memory pool size"
715 depends on DEBUG_KMEMLEAK
719 Kmemleak must track all the memory allocations to avoid
720 reporting false positives. Since memory may be allocated or
721 freed before kmemleak is fully initialised, use a static pool
722 of metadata objects to track such callbacks. After kmemleak is
723 fully initialised, this memory pool acts as an emergency one
724 if slab allocations fail.
726 config DEBUG_KMEMLEAK_TEST
727 tristate "Simple test for the kernel memory leak detector"
728 depends on DEBUG_KMEMLEAK && m
730 This option enables a module that explicitly leaks memory.
734 config DEBUG_KMEMLEAK_DEFAULT_OFF
735 bool "Default kmemleak to off"
736 depends on DEBUG_KMEMLEAK
738 Say Y here to disable kmemleak by default. It can then be enabled
739 on the command line via kmemleak=on.
741 config DEBUG_KMEMLEAK_AUTO_SCAN
742 bool "Enable kmemleak auto scan thread on boot up"
744 depends on DEBUG_KMEMLEAK
746 Depending on the cpu, kmemleak scan may be cpu intensive and can
747 stall user tasks at times. This option enables/disables automatic
748 kmemleak scan at boot up.
750 Say N here to disable kmemleak auto scan thread to stop automatic
751 scanning. Disabling this option disables automatic reporting of
756 config DEBUG_STACK_USAGE
757 bool "Stack utilization instrumentation"
758 depends on DEBUG_KERNEL && !IA64
760 Enables the display of the minimum amount of free stack which each
761 task has ever had available in the sysrq-T and sysrq-P debug output.
763 This option will slow down process creation somewhat.
765 config SCHED_STACK_END_CHECK
766 bool "Detect stack corruption on calls to schedule()"
767 depends on DEBUG_KERNEL
770 This option checks for a stack overrun on calls to schedule().
771 If the stack end location is found to be over written always panic as
772 the content of the corrupted region can no longer be trusted.
773 This is to ensure no erroneous behaviour occurs which could result in
774 data corruption or a sporadic crash at a later stage once the region
775 is examined. The runtime overhead introduced is minimal.
777 config ARCH_HAS_DEBUG_VM_PGTABLE
780 An architecture should select this when it can successfully
781 build and run DEBUG_VM_PGTABLE.
785 depends on DEBUG_KERNEL
787 Enable this to turn on extended checks in the virtual-memory system
788 that may impact performance.
792 config DEBUG_VM_VMACACHE
793 bool "Debug VMA caching"
796 Enable this to turn on VMA caching debug information. Doing so
797 can cause significant overhead, so only enable it in non-production
803 bool "Debug VM red-black trees"
806 Enable VM red-black tree debugging information and extra validations.
810 config DEBUG_VM_PGFLAGS
811 bool "Debug page-flags operations"
814 Enables extra validation on page flags operations.
818 config DEBUG_VM_PGTABLE
819 bool "Debug arch page table for semantics compliance"
821 depends on ARCH_HAS_DEBUG_VM_PGTABLE
822 default y if DEBUG_VM
824 This option provides a debug method which can be used to test
825 architecture page table helper functions on various platforms in
826 verifying if they comply with expected generic MM semantics. This
827 will help architecture code in making sure that any changes or
828 new additions of these helpers still conform to expected
829 semantics of the generic MM. Platforms will have to opt in for
830 this through ARCH_HAS_DEBUG_VM_PGTABLE.
834 config ARCH_HAS_DEBUG_VIRTUAL
838 bool "Debug VM translations"
839 depends on DEBUG_KERNEL && ARCH_HAS_DEBUG_VIRTUAL
841 Enable some costly sanity checks in virtual to page code. This can
842 catch mistakes with virt_to_page() and friends.
846 config DEBUG_NOMMU_REGIONS
847 bool "Debug the global anon/private NOMMU mapping region tree"
848 depends on DEBUG_KERNEL && !MMU
850 This option causes the global tree of anonymous and private mapping
851 regions to be regularly checked for invalid topology.
853 config DEBUG_MEMORY_INIT
854 bool "Debug memory initialisation" if EXPERT
857 Enable this for additional checks during memory initialisation.
858 The sanity checks verify aspects of the VM such as the memory model
859 and other information provided by the architecture. Verbose
860 information will be printed at KERN_DEBUG loglevel depending
861 on the mminit_loglevel= command-line option.
865 config MEMORY_NOTIFIER_ERROR_INJECT
866 tristate "Memory hotplug notifier error injection module"
867 depends on MEMORY_HOTPLUG_SPARSE && NOTIFIER_ERROR_INJECTION
869 This option provides the ability to inject artificial errors to
870 memory hotplug notifier chain callbacks. It is controlled through
871 debugfs interface under /sys/kernel/debug/notifier-error-inject/memory
873 If the notifier call chain should be failed with some events
874 notified, write the error code to "actions/<notifier event>/error".
876 Example: Inject memory hotplug offline error (-12 == -ENOMEM)
878 # cd /sys/kernel/debug/notifier-error-inject/memory
879 # echo -12 > actions/MEM_GOING_OFFLINE/error
880 # echo offline > /sys/devices/system/memory/memoryXXX/state
881 bash: echo: write error: Cannot allocate memory
883 To compile this code as a module, choose M here: the module will
884 be called memory-notifier-error-inject.
888 config DEBUG_PER_CPU_MAPS
889 bool "Debug access to per_cpu maps"
890 depends on DEBUG_KERNEL
893 Say Y to verify that the per_cpu map being accessed has
894 been set up. This adds a fair amount of code to kernel memory
895 and decreases performance.
899 config DEBUG_KMAP_LOCAL
900 bool "Debug kmap_local temporary mappings"
901 depends on DEBUG_KERNEL && KMAP_LOCAL
903 This option enables additional error checking for the kmap_local
904 infrastructure. Disable for production use.
906 config ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
909 config DEBUG_KMAP_LOCAL_FORCE_MAP
910 bool "Enforce kmap_local temporary mappings"
911 depends on DEBUG_KERNEL && ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
913 select DEBUG_KMAP_LOCAL
915 This option enforces temporary mappings through the kmap_local
916 mechanism for non-highmem pages and on non-highmem systems.
917 Disable this for production systems!
920 bool "Highmem debugging"
921 depends on DEBUG_KERNEL && HIGHMEM
922 select DEBUG_KMAP_LOCAL_FORCE_MAP if ARCH_SUPPORTS_KMAP_LOCAL_FORCE_MAP
923 select DEBUG_KMAP_LOCAL
925 This option enables additional error checking for high memory
926 systems. Disable for production systems.
928 config HAVE_DEBUG_STACKOVERFLOW
931 config DEBUG_STACKOVERFLOW
932 bool "Check for stack overflows"
933 depends on DEBUG_KERNEL && HAVE_DEBUG_STACKOVERFLOW
935 Say Y here if you want to check for overflows of kernel, IRQ
936 and exception stacks (if your architecture uses them). This
937 option will show detailed messages if free stack space drops
938 below a certain limit.
940 These kinds of bugs usually occur when call-chains in the
941 kernel get too deep, especially when interrupts are
944 Use this in cases where you see apparently random memory
945 corruption, especially if it appears in 'struct thread_info'
947 If in doubt, say "N".
949 source "lib/Kconfig.kasan"
950 source "lib/Kconfig.kfence"
952 endmenu # "Memory Debugging"
955 bool "Debug shared IRQ handlers"
956 depends on DEBUG_KERNEL
958 Enable this to generate a spurious interrupt just before a shared
959 interrupt handler is deregistered (generating one when registering
960 is currently disabled). Drivers need to handle this correctly. Some
961 don't and need to be caught.
963 menu "Debug Oops, Lockups and Hangs"
968 Say Y here to enable the kernel to panic when it oopses. This
969 has the same effect as setting oops=panic on the kernel command
972 This feature is useful to ensure that the kernel does not do
973 anything erroneous after an oops which could result in data
974 corruption or other issues.
978 config PANIC_ON_OOPS_VALUE
981 default 0 if !PANIC_ON_OOPS
982 default 1 if PANIC_ON_OOPS
988 Set the timeout value (in seconds) until a reboot occurs when
989 the kernel panics. If n = 0, then we wait forever. A timeout
990 value n > 0 will wait n seconds before rebooting, while a timeout
991 value n < 0 will reboot immediately.
993 config LOCKUP_DETECTOR
996 config SOFTLOCKUP_DETECTOR
997 bool "Detect Soft Lockups"
998 depends on DEBUG_KERNEL && !S390
999 select LOCKUP_DETECTOR
1001 Say Y here to enable the kernel to act as a watchdog to detect
1004 Softlockups are bugs that cause the kernel to loop in kernel
1005 mode for more than 20 seconds, without giving other tasks a
1006 chance to run. The current stack trace is displayed upon
1007 detection and the system will stay locked up.
1009 config BOOTPARAM_SOFTLOCKUP_PANIC
1010 bool "Panic (Reboot) On Soft Lockups"
1011 depends on SOFTLOCKUP_DETECTOR
1013 Say Y here to enable the kernel to panic on "soft lockups",
1014 which are bugs that cause the kernel to loop in kernel
1015 mode for more than 20 seconds (configurable using the watchdog_thresh
1016 sysctl), without giving other tasks a chance to run.
1018 The panic can be used in combination with panic_timeout,
1019 to cause the system to reboot automatically after a
1020 lockup has been detected. This feature is useful for
1021 high-availability systems that have uptime guarantees and
1022 where a lockup must be resolved ASAP.
1026 config BOOTPARAM_SOFTLOCKUP_PANIC_VALUE
1028 depends on SOFTLOCKUP_DETECTOR
1030 default 0 if !BOOTPARAM_SOFTLOCKUP_PANIC
1031 default 1 if BOOTPARAM_SOFTLOCKUP_PANIC
1033 config HARDLOCKUP_DETECTOR_PERF
1035 select SOFTLOCKUP_DETECTOR
1038 # Enables a timestamp based low pass filter to compensate for perf based
1039 # hard lockup detection which runs too fast due to turbo modes.
1041 config HARDLOCKUP_CHECK_TIMESTAMP
1045 # arch/ can define HAVE_HARDLOCKUP_DETECTOR_ARCH to provide their own hard
1046 # lockup detector rather than the perf based detector.
1048 config HARDLOCKUP_DETECTOR
1049 bool "Detect Hard Lockups"
1050 depends on DEBUG_KERNEL && !S390
1051 depends on HAVE_HARDLOCKUP_DETECTOR_PERF || HAVE_HARDLOCKUP_DETECTOR_ARCH
1052 select LOCKUP_DETECTOR
1053 select HARDLOCKUP_DETECTOR_PERF if HAVE_HARDLOCKUP_DETECTOR_PERF
1054 select HARDLOCKUP_DETECTOR_ARCH if HAVE_HARDLOCKUP_DETECTOR_ARCH
1056 Say Y here to enable the kernel to act as a watchdog to detect
1059 Hardlockups are bugs that cause the CPU to loop in kernel mode
1060 for more than 10 seconds, without letting other interrupts have a
1061 chance to run. The current stack trace is displayed upon detection
1062 and the system will stay locked up.
1064 config BOOTPARAM_HARDLOCKUP_PANIC
1065 bool "Panic (Reboot) On Hard Lockups"
1066 depends on HARDLOCKUP_DETECTOR
1068 Say Y here to enable the kernel to panic on "hard lockups",
1069 which are bugs that cause the kernel to loop in kernel
1070 mode with interrupts disabled for more than 10 seconds (configurable
1071 using the watchdog_thresh sysctl).
1075 config BOOTPARAM_HARDLOCKUP_PANIC_VALUE
1077 depends on HARDLOCKUP_DETECTOR
1079 default 0 if !BOOTPARAM_HARDLOCKUP_PANIC
1080 default 1 if BOOTPARAM_HARDLOCKUP_PANIC
1082 config DETECT_HUNG_TASK
1083 bool "Detect Hung Tasks"
1084 depends on DEBUG_KERNEL
1085 default SOFTLOCKUP_DETECTOR
1087 Say Y here to enable the kernel to detect "hung tasks",
1088 which are bugs that cause the task to be stuck in
1089 uninterruptible "D" state indefinitely.
1091 When a hung task is detected, the kernel will print the
1092 current stack trace (which you should report), but the
1093 task will stay in uninterruptible state. If lockdep is
1094 enabled then all held locks will also be reported. This
1095 feature has negligible overhead.
1097 config DEFAULT_HUNG_TASK_TIMEOUT
1098 int "Default timeout for hung task detection (in seconds)"
1099 depends on DETECT_HUNG_TASK
1102 This option controls the default timeout (in seconds) used
1103 to determine when a task has become non-responsive and should
1106 It can be adjusted at runtime via the kernel.hung_task_timeout_secs
1107 sysctl or by writing a value to
1108 /proc/sys/kernel/hung_task_timeout_secs.
1110 A timeout of 0 disables the check. The default is two minutes.
1111 Keeping the default should be fine in most cases.
1113 config BOOTPARAM_HUNG_TASK_PANIC
1114 bool "Panic (Reboot) On Hung Tasks"
1115 depends on DETECT_HUNG_TASK
1117 Say Y here to enable the kernel to panic on "hung tasks",
1118 which are bugs that cause the kernel to leave a task stuck
1119 in uninterruptible "D" state.
1121 The panic can be used in combination with panic_timeout,
1122 to cause the system to reboot automatically after a
1123 hung task has been detected. This feature is useful for
1124 high-availability systems that have uptime guarantees and
1125 where a hung tasks must be resolved ASAP.
1129 config BOOTPARAM_HUNG_TASK_PANIC_VALUE
1131 depends on DETECT_HUNG_TASK
1133 default 0 if !BOOTPARAM_HUNG_TASK_PANIC
1134 default 1 if BOOTPARAM_HUNG_TASK_PANIC
1137 bool "Detect Workqueue Stalls"
1138 depends on DEBUG_KERNEL
1140 Say Y here to enable stall detection on workqueues. If a
1141 worker pool doesn't make forward progress on a pending work
1142 item for over a given amount of time, 30s by default, a
1143 warning message is printed along with dump of workqueue
1144 state. This can be configured through kernel parameter
1145 "workqueue.watchdog_thresh" and its sysfs counterpart.
1148 tristate "Test module to generate lockups"
1151 This builds the "test_lockup" module that helps to make sure
1152 that watchdogs and lockup detectors are working properly.
1154 Depending on module parameters it could emulate soft or hard
1155 lockup, "hung task", or locking arbitrary lock for a long time.
1156 Also it could generate series of lockups with cooling-down periods.
1160 endmenu # "Debug lockups and hangs"
1162 menu "Scheduler Debugging"
1165 bool "Collect scheduler debugging info"
1166 depends on DEBUG_KERNEL && PROC_FS
1169 If you say Y here, the /proc/sched_debug file will be provided
1170 that can help debug the scheduler. The runtime overhead of this
1178 bool "Collect scheduler statistics"
1179 depends on DEBUG_KERNEL && PROC_FS
1182 If you say Y here, additional code will be inserted into the
1183 scheduler and related routines to collect statistics about
1184 scheduler behavior and provide them in /proc/schedstat. These
1185 stats may be useful for both tuning and debugging the scheduler
1186 If you aren't debugging the scheduler or trying to tune a specific
1187 application, you can say N to avoid the very slight overhead
1192 config DEBUG_TIMEKEEPING
1193 bool "Enable extra timekeeping sanity checking"
1195 This option will enable additional timekeeping sanity checks
1196 which may be helpful when diagnosing issues where timekeeping
1197 problems are suspected.
1199 This may include checks in the timekeeping hotpaths, so this
1200 option may have a (very small) performance impact to some
1205 config DEBUG_PREEMPT
1206 bool "Debug preemptible kernel"
1207 depends on DEBUG_KERNEL && PREEMPTION && TRACE_IRQFLAGS_SUPPORT
1210 If you say Y here then the kernel will use a debug variant of the
1211 commonly used smp_processor_id() function and will print warnings
1212 if kernel code uses it in a preemption-unsafe way. Also, the kernel
1213 will detect preemption count underflows.
1215 menu "Lock Debugging (spinlocks, mutexes, etc...)"
1217 config LOCK_DEBUGGING_SUPPORT
1219 depends on TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
1222 config PROVE_LOCKING
1223 bool "Lock debugging: prove locking correctness"
1224 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1226 select DEBUG_SPINLOCK
1227 select DEBUG_MUTEXES
1228 select DEBUG_RT_MUTEXES if RT_MUTEXES
1230 select DEBUG_WW_MUTEX_SLOWPATH
1231 select DEBUG_LOCK_ALLOC
1232 select PREEMPT_COUNT if !ARCH_NO_PREEMPT
1233 select TRACE_IRQFLAGS
1236 This feature enables the kernel to prove that all locking
1237 that occurs in the kernel runtime is mathematically
1238 correct: that under no circumstance could an arbitrary (and
1239 not yet triggered) combination of observed locking
1240 sequences (on an arbitrary number of CPUs, running an
1241 arbitrary number of tasks and interrupt contexts) cause a
1244 In short, this feature enables the kernel to report locking
1245 related deadlocks before they actually occur.
1247 The proof does not depend on how hard and complex a
1248 deadlock scenario would be to trigger: how many
1249 participant CPUs, tasks and irq-contexts would be needed
1250 for it to trigger. The proof also does not depend on
1251 timing: if a race and a resulting deadlock is possible
1252 theoretically (no matter how unlikely the race scenario
1253 is), it will be proven so and will immediately be
1254 reported by the kernel (once the event is observed that
1255 makes the deadlock theoretically possible).
1257 If a deadlock is impossible (i.e. the locking rules, as
1258 observed by the kernel, are mathematically correct), the
1259 kernel reports nothing.
1261 NOTE: this feature can also be enabled for rwlocks, mutexes
1262 and rwsems - in which case all dependencies between these
1263 different locking variants are observed and mapped too, and
1264 the proof of observed correctness is also maintained for an
1265 arbitrary combination of these separate locking variants.
1267 For more details, see Documentation/locking/lockdep-design.rst.
1269 config PROVE_RAW_LOCK_NESTING
1270 bool "Enable raw_spinlock - spinlock nesting checks"
1271 depends on PROVE_LOCKING
1274 Enable the raw_spinlock vs. spinlock nesting checks which ensure
1275 that the lock nesting rules for PREEMPT_RT enabled kernels are
1278 NOTE: There are known nesting problems. So if you enable this
1279 option expect lockdep splats until these problems have been fully
1280 addressed which is work in progress. This config switch allows to
1281 identify and analyze these problems. It will be removed and the
1282 check permanentely enabled once the main issues have been fixed.
1284 If unsure, select N.
1287 bool "Lock usage statistics"
1288 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1290 select DEBUG_SPINLOCK
1291 select DEBUG_MUTEXES
1292 select DEBUG_RT_MUTEXES if RT_MUTEXES
1293 select DEBUG_LOCK_ALLOC
1296 This feature enables tracking lock contention points
1298 For more details, see Documentation/locking/lockstat.rst
1300 This also enables lock events required by "perf lock",
1302 If you want to use "perf lock", you also need to turn on
1303 CONFIG_EVENT_TRACING.
1305 CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
1306 (CONFIG_LOCKDEP defines "acquire" and "release" events.)
1308 config DEBUG_RT_MUTEXES
1309 bool "RT Mutex debugging, deadlock detection"
1310 depends on DEBUG_KERNEL && RT_MUTEXES
1312 This allows rt mutex semantics violations and rt mutex related
1313 deadlocks (lockups) to be detected and reported automatically.
1315 config DEBUG_SPINLOCK
1316 bool "Spinlock and rw-lock debugging: basic checks"
1317 depends on DEBUG_KERNEL
1318 select UNINLINE_SPIN_UNLOCK
1320 Say Y here and build SMP to catch missing spinlock initialization
1321 and certain other kinds of spinlock errors commonly made. This is
1322 best used in conjunction with the NMI watchdog so that spinlock
1323 deadlocks are also debuggable.
1325 config DEBUG_MUTEXES
1326 bool "Mutex debugging: basic checks"
1327 depends on DEBUG_KERNEL
1329 This feature allows mutex semantics violations to be detected and
1332 config DEBUG_WW_MUTEX_SLOWPATH
1333 bool "Wait/wound mutex debugging: Slowpath testing"
1334 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1335 select DEBUG_LOCK_ALLOC
1336 select DEBUG_SPINLOCK
1337 select DEBUG_MUTEXES
1339 This feature enables slowpath testing for w/w mutex users by
1340 injecting additional -EDEADLK wound/backoff cases. Together with
1341 the full mutex checks enabled with (CONFIG_PROVE_LOCKING) this
1342 will test all possible w/w mutex interface abuse with the
1343 exception of simply not acquiring all the required locks.
1344 Note that this feature can introduce significant overhead, so
1345 it really should not be enabled in a production or distro kernel,
1346 even a debug kernel. If you are a driver writer, enable it. If
1347 you are a distro, do not.
1350 bool "RW Semaphore debugging: basic checks"
1351 depends on DEBUG_KERNEL
1353 This debugging feature allows mismatched rw semaphore locks
1354 and unlocks to be detected and reported.
1356 config DEBUG_LOCK_ALLOC
1357 bool "Lock debugging: detect incorrect freeing of live locks"
1358 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1359 select DEBUG_SPINLOCK
1360 select DEBUG_MUTEXES
1361 select DEBUG_RT_MUTEXES if RT_MUTEXES
1364 This feature will check whether any held lock (spinlock, rwlock,
1365 mutex or rwsem) is incorrectly freed by the kernel, via any of the
1366 memory-freeing routines (kfree(), kmem_cache_free(), free_pages(),
1367 vfree(), etc.), whether a live lock is incorrectly reinitialized via
1368 spin_lock_init()/mutex_init()/etc., or whether there is any lock
1369 held during task exit.
1373 depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
1375 depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
1379 config LOCKDEP_SMALL
1383 int "Bitsize for MAX_LOCKDEP_ENTRIES"
1384 depends on LOCKDEP && !LOCKDEP_SMALL
1388 Try increasing this value if you hit "BUG: MAX_LOCKDEP_ENTRIES too low!" message.
1390 config LOCKDEP_CHAINS_BITS
1391 int "Bitsize for MAX_LOCKDEP_CHAINS"
1392 depends on LOCKDEP && !LOCKDEP_SMALL
1396 Try increasing this value if you hit "BUG: MAX_LOCKDEP_CHAINS too low!" message.
1398 config LOCKDEP_STACK_TRACE_BITS
1399 int "Bitsize for MAX_STACK_TRACE_ENTRIES"
1400 depends on LOCKDEP && !LOCKDEP_SMALL
1404 Try increasing this value if you hit "BUG: MAX_STACK_TRACE_ENTRIES too low!" message.
1406 config LOCKDEP_STACK_TRACE_HASH_BITS
1407 int "Bitsize for STACK_TRACE_HASH_SIZE"
1408 depends on LOCKDEP && !LOCKDEP_SMALL
1412 Try increasing this value if you need large MAX_STACK_TRACE_ENTRIES.
1414 config LOCKDEP_CIRCULAR_QUEUE_BITS
1415 int "Bitsize for elements in circular_queue struct"
1420 Try increasing this value if you hit "lockdep bfs error:-1" warning due to __cq_enqueue() failure.
1422 config DEBUG_LOCKDEP
1423 bool "Lock dependency engine debugging"
1424 depends on DEBUG_KERNEL && LOCKDEP
1425 select DEBUG_IRQFLAGS
1427 If you say Y here, the lock dependency engine will do
1428 additional runtime checks to debug itself, at the price
1429 of more runtime overhead.
1431 config DEBUG_ATOMIC_SLEEP
1432 bool "Sleep inside atomic section checking"
1433 select PREEMPT_COUNT
1434 depends on DEBUG_KERNEL
1435 depends on !ARCH_NO_PREEMPT
1437 If you say Y here, various routines which may sleep will become very
1438 noisy if they are called inside atomic sections: when a spinlock is
1439 held, inside an rcu read side critical section, inside preempt disabled
1440 sections, inside an interrupt, etc...
1442 config DEBUG_LOCKING_API_SELFTESTS
1443 bool "Locking API boot-time self-tests"
1444 depends on DEBUG_KERNEL
1446 Say Y here if you want the kernel to run a short self-test during
1447 bootup. The self-test checks whether common types of locking bugs
1448 are detected by debugging mechanisms or not. (if you disable
1449 lock debugging then those bugs wont be detected of course.)
1450 The following locking APIs are covered: spinlocks, rwlocks,
1453 config LOCK_TORTURE_TEST
1454 tristate "torture tests for locking"
1455 depends on DEBUG_KERNEL
1458 This option provides a kernel module that runs torture tests
1459 on kernel locking primitives. The kernel module may be built
1460 after the fact on the running kernel to be tested, if desired.
1462 Say Y here if you want kernel locking-primitive torture tests
1463 to be built into the kernel.
1464 Say M if you want these torture tests to build as a module.
1465 Say N if you are unsure.
1467 config WW_MUTEX_SELFTEST
1468 tristate "Wait/wound mutex selftests"
1470 This option provides a kernel module that runs tests on the
1471 on the struct ww_mutex locking API.
1473 It is recommended to enable DEBUG_WW_MUTEX_SLOWPATH in conjunction
1474 with this test harness.
1476 Say M if you want these self tests to build as a module.
1477 Say N if you are unsure.
1479 config SCF_TORTURE_TEST
1480 tristate "torture tests for smp_call_function*()"
1481 depends on DEBUG_KERNEL
1484 This option provides a kernel module that runs torture tests
1485 on the smp_call_function() family of primitives. The kernel
1486 module may be built after the fact on the running kernel to
1487 be tested, if desired.
1489 config CSD_LOCK_WAIT_DEBUG
1490 bool "Debugging for csd_lock_wait(), called from smp_call_function*()"
1491 depends on DEBUG_KERNEL
1495 This option enables debug prints when CPUs are slow to respond
1496 to the smp_call_function*() IPI wrappers. These debug prints
1497 include the IPI handler function currently executing (if any)
1498 and relevant stack traces.
1500 endmenu # lock debugging
1502 config TRACE_IRQFLAGS
1503 depends on TRACE_IRQFLAGS_SUPPORT
1506 Enables hooks to interrupt enabling and disabling for
1507 either tracing or lock debugging.
1509 config TRACE_IRQFLAGS_NMI
1511 depends on TRACE_IRQFLAGS
1512 depends on TRACE_IRQFLAGS_NMI_SUPPORT
1514 config DEBUG_IRQFLAGS
1515 bool "Debug IRQ flag manipulation"
1517 Enables checks for potentially unsafe enabling or disabling of
1518 interrupts, such as calling raw_local_irq_restore() when interrupts
1522 bool "Stack backtrace support"
1523 depends on STACKTRACE_SUPPORT
1525 This option causes the kernel to create a /proc/pid/stack for
1526 every process, showing its current stack trace.
1527 It is also used by various kernel debugging features that require
1528 stack trace generation.
1530 config WARN_ALL_UNSEEDED_RANDOM
1531 bool "Warn for all uses of unseeded randomness"
1534 Some parts of the kernel contain bugs relating to their use of
1535 cryptographically secure random numbers before it's actually possible
1536 to generate those numbers securely. This setting ensures that these
1537 flaws don't go unnoticed, by enabling a message, should this ever
1538 occur. This will allow people with obscure setups to know when things
1539 are going wrong, so that they might contact developers about fixing
1542 Unfortunately, on some models of some architectures getting
1543 a fully seeded CRNG is extremely difficult, and so this can
1544 result in dmesg getting spammed for a surprisingly long
1545 time. This is really bad from a security perspective, and
1546 so architecture maintainers really need to do what they can
1547 to get the CRNG seeded sooner after the system is booted.
1548 However, since users cannot do anything actionable to
1549 address this, by default the kernel will issue only a single
1550 warning for the first use of unseeded randomness.
1552 Say Y here if you want to receive warnings for all uses of
1553 unseeded randomness. This will be of use primarily for
1554 those developers interested in improving the security of
1555 Linux kernels running on their architecture (or
1558 config DEBUG_KOBJECT
1559 bool "kobject debugging"
1560 depends on DEBUG_KERNEL
1562 If you say Y here, some extra kobject debugging messages will be sent
1565 config DEBUG_KOBJECT_RELEASE
1566 bool "kobject release debugging"
1567 depends on DEBUG_OBJECTS_TIMERS
1569 kobjects are reference counted objects. This means that their
1570 last reference count put is not predictable, and the kobject can
1571 live on past the point at which a driver decides to drop it's
1572 initial reference to the kobject gained on allocation. An
1573 example of this would be a struct device which has just been
1576 However, some buggy drivers assume that after such an operation,
1577 the memory backing the kobject can be immediately freed. This
1578 goes completely against the principles of a refcounted object.
1580 If you say Y here, the kernel will delay the release of kobjects
1581 on the last reference count to improve the visibility of this
1582 kind of kobject release bug.
1584 config HAVE_DEBUG_BUGVERBOSE
1587 menu "Debug kernel data structures"
1590 bool "Debug linked list manipulation"
1591 depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION
1593 Enable this to turn on extended checks in the linked-list
1599 bool "Debug priority linked list manipulation"
1600 depends on DEBUG_KERNEL
1602 Enable this to turn on extended checks in the priority-ordered
1603 linked-list (plist) walking routines. This checks the entire
1604 list multiple times during each manipulation.
1609 bool "Debug SG table operations"
1610 depends on DEBUG_KERNEL
1612 Enable this to turn on checks on scatter-gather tables. This can
1613 help find problems with drivers that do not properly initialize
1618 config DEBUG_NOTIFIERS
1619 bool "Debug notifier call chains"
1620 depends on DEBUG_KERNEL
1622 Enable this to turn on sanity checking for notifier call chains.
1623 This is most useful for kernel developers to make sure that
1624 modules properly unregister themselves from notifier chains.
1625 This is a relatively cheap check but if you care about maximum
1628 config BUG_ON_DATA_CORRUPTION
1629 bool "Trigger a BUG when data corruption is detected"
1632 Select this option if the kernel should BUG when it encounters
1633 data corruption in kernel memory structures when they get checked
1640 config DEBUG_CREDENTIALS
1641 bool "Debug credential management"
1642 depends on DEBUG_KERNEL
1644 Enable this to turn on some debug checking for credential
1645 management. The additional code keeps track of the number of
1646 pointers from task_structs to any given cred struct, and checks to
1647 see that this number never exceeds the usage count of the cred
1650 Furthermore, if SELinux is enabled, this also checks that the
1651 security pointer in the cred struct is never seen to be invalid.
1655 source "kernel/rcu/Kconfig.debug"
1657 config DEBUG_WQ_FORCE_RR_CPU
1658 bool "Force round-robin CPU selection for unbound work items"
1659 depends on DEBUG_KERNEL
1662 Workqueue used to implicitly guarantee that work items queued
1663 without explicit CPU specified are put on the local CPU. This
1664 guarantee is no longer true and while local CPU is still
1665 preferred work items may be put on foreign CPUs. Kernel
1666 parameter "workqueue.debug_force_rr_cpu" is added to force
1667 round-robin CPU selection to flush out usages which depend on the
1668 now broken guarantee. This config option enables the debug
1669 feature by default. When enabled, memory and cache locality will
1672 config DEBUG_BLOCK_EXT_DEVT
1673 bool "Force extended block device numbers and spread them"
1674 depends on DEBUG_KERNEL
1678 BIG FAT WARNING: ENABLING THIS OPTION MIGHT BREAK BOOTING ON
1679 SOME DISTRIBUTIONS. DO NOT ENABLE THIS UNLESS YOU KNOW WHAT
1680 YOU ARE DOING. Distros, please enable this and fix whatever
1683 Conventionally, block device numbers are allocated from
1684 predetermined contiguous area. However, extended block area
1685 may introduce non-contiguous block device numbers. This
1686 option forces most block device numbers to be allocated from
1687 the extended space and spreads them to discover kernel or
1688 userland code paths which assume predetermined contiguous
1689 device number allocation.
1691 Note that turning on this debug option shuffles all the
1692 device numbers for all IDE and SCSI devices including libata
1693 ones, so root partition specified using device number
1694 directly (via rdev or root=MAJ:MIN) won't work anymore.
1695 Textual device names (root=/dev/sdXn) will continue to work.
1697 Say N if you are unsure.
1699 config CPU_HOTPLUG_STATE_CONTROL
1700 bool "Enable CPU hotplug state control"
1701 depends on DEBUG_KERNEL
1702 depends on HOTPLUG_CPU
1705 Allows to write steps between "offline" and "online" to the CPUs
1706 sysfs target file so states can be stepped granular. This is a debug
1707 option for now as the hotplug machinery cannot be stopped and
1708 restarted at arbitrary points yet.
1710 Say N if your are unsure.
1713 bool "Latency measuring infrastructure"
1714 depends on DEBUG_KERNEL
1715 depends on STACKTRACE_SUPPORT
1717 depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
1723 Enable this option if you want to use the LatencyTOP tool
1724 to find out which userspace is blocking on what kernel operations.
1726 source "kernel/trace/Kconfig"
1728 config PROVIDE_OHCI1394_DMA_INIT
1729 bool "Remote debugging over FireWire early on boot"
1730 depends on PCI && X86
1732 If you want to debug problems which hang or crash the kernel early
1733 on boot and the crashing machine has a FireWire port, you can use
1734 this feature to remotely access the memory of the crashed machine
1735 over FireWire. This employs remote DMA as part of the OHCI1394
1736 specification which is now the standard for FireWire controllers.
1738 With remote DMA, you can monitor the printk buffer remotely using
1739 firescope and access all memory below 4GB using fireproxy from gdb.
1740 Even controlling a kernel debugger is possible using remote DMA.
1744 If ohci1394_dma=early is used as boot parameter, it will initialize
1745 all OHCI1394 controllers which are found in the PCI config space.
1747 As all changes to the FireWire bus such as enabling and disabling
1748 devices cause a bus reset and thereby disable remote DMA for all
1749 devices, be sure to have the cable plugged and FireWire enabled on
1750 the debugging host before booting the debug target for debugging.
1752 This code (~1k) is freed after boot. By then, the firewire stack
1753 in charge of the OHCI-1394 controllers should be used instead.
1755 See Documentation/core-api/debugging-via-ohci1394.rst for more information.
1757 source "samples/Kconfig"
1759 config ARCH_HAS_DEVMEM_IS_ALLOWED
1762 config STRICT_DEVMEM
1763 bool "Filter access to /dev/mem"
1764 depends on MMU && DEVMEM
1765 depends on ARCH_HAS_DEVMEM_IS_ALLOWED || GENERIC_LIB_DEVMEM_IS_ALLOWED
1766 default y if PPC || X86 || ARM64
1768 If this option is disabled, you allow userspace (root) access to all
1769 of memory, including kernel and userspace memory. Accidental
1770 access to this is obviously disastrous, but specific access can
1771 be used by people debugging the kernel. Note that with PAT support
1772 enabled, even in this case there are restrictions on /dev/mem
1773 use due to the cache aliasing requirements.
1775 If this option is switched on, and IO_STRICT_DEVMEM=n, the /dev/mem
1776 file only allows userspace access to PCI space and the BIOS code and
1777 data regions. This is sufficient for dosemu and X and all common
1782 config IO_STRICT_DEVMEM
1783 bool "Filter I/O access to /dev/mem"
1784 depends on STRICT_DEVMEM
1786 If this option is disabled, you allow userspace (root) access to all
1787 io-memory regardless of whether a driver is actively using that
1788 range. Accidental access to this is obviously disastrous, but
1789 specific access can be used by people debugging kernel drivers.
1791 If this option is switched on, the /dev/mem file only allows
1792 userspace access to *idle* io-memory ranges (see /proc/iomem) This
1793 may break traditional users of /dev/mem (dosemu, legacy X, etc...)
1794 if the driver using a given range cannot be disabled.
1798 menu "$(SRCARCH) Debugging"
1800 source "arch/$(SRCARCH)/Kconfig.debug"
1804 menu "Kernel Testing and Coverage"
1806 source "lib/kunit/Kconfig"
1808 config NOTIFIER_ERROR_INJECTION
1809 tristate "Notifier error injection"
1810 depends on DEBUG_KERNEL
1813 This option provides the ability to inject artificial errors to
1814 specified notifier chain callbacks. It is useful to test the error
1815 handling of notifier call chain failures.
1819 config PM_NOTIFIER_ERROR_INJECT
1820 tristate "PM notifier error injection module"
1821 depends on PM && NOTIFIER_ERROR_INJECTION
1822 default m if PM_DEBUG
1824 This option provides the ability to inject artificial errors to
1825 PM notifier chain callbacks. It is controlled through debugfs
1826 interface /sys/kernel/debug/notifier-error-inject/pm
1828 If the notifier call chain should be failed with some events
1829 notified, write the error code to "actions/<notifier event>/error".
1831 Example: Inject PM suspend error (-12 = -ENOMEM)
1833 # cd /sys/kernel/debug/notifier-error-inject/pm/
1834 # echo -12 > actions/PM_SUSPEND_PREPARE/error
1835 # echo mem > /sys/power/state
1836 bash: echo: write error: Cannot allocate memory
1838 To compile this code as a module, choose M here: the module will
1839 be called pm-notifier-error-inject.
1843 config OF_RECONFIG_NOTIFIER_ERROR_INJECT
1844 tristate "OF reconfig notifier error injection module"
1845 depends on OF_DYNAMIC && NOTIFIER_ERROR_INJECTION
1847 This option provides the ability to inject artificial errors to
1848 OF reconfig notifier chain callbacks. It is controlled
1849 through debugfs interface under
1850 /sys/kernel/debug/notifier-error-inject/OF-reconfig/
1852 If the notifier call chain should be failed with some events
1853 notified, write the error code to "actions/<notifier event>/error".
1855 To compile this code as a module, choose M here: the module will
1856 be called of-reconfig-notifier-error-inject.
1860 config NETDEV_NOTIFIER_ERROR_INJECT
1861 tristate "Netdev notifier error injection module"
1862 depends on NET && NOTIFIER_ERROR_INJECTION
1864 This option provides the ability to inject artificial errors to
1865 netdevice notifier chain callbacks. It is controlled through debugfs
1866 interface /sys/kernel/debug/notifier-error-inject/netdev
1868 If the notifier call chain should be failed with some events
1869 notified, write the error code to "actions/<notifier event>/error".
1871 Example: Inject netdevice mtu change error (-22 = -EINVAL)
1873 # cd /sys/kernel/debug/notifier-error-inject/netdev
1874 # echo -22 > actions/NETDEV_CHANGEMTU/error
1875 # ip link set eth0 mtu 1024
1876 RTNETLINK answers: Invalid argument
1878 To compile this code as a module, choose M here: the module will
1879 be called netdev-notifier-error-inject.
1883 config FUNCTION_ERROR_INJECTION
1885 depends on HAVE_FUNCTION_ERROR_INJECTION && KPROBES
1887 config FAULT_INJECTION
1888 bool "Fault-injection framework"
1889 depends on DEBUG_KERNEL
1891 Provide fault-injection framework.
1892 For more details, see Documentation/fault-injection/.
1895 bool "Fault-injection capability for kmalloc"
1896 depends on FAULT_INJECTION
1897 depends on SLAB || SLUB
1899 Provide fault-injection capability for kmalloc.
1901 config FAIL_PAGE_ALLOC
1902 bool "Fault-injection capability for alloc_pages()"
1903 depends on FAULT_INJECTION
1905 Provide fault-injection capability for alloc_pages().
1907 config FAULT_INJECTION_USERCOPY
1908 bool "Fault injection capability for usercopy functions"
1909 depends on FAULT_INJECTION
1911 Provides fault-injection capability to inject failures
1912 in usercopy functions (copy_from_user(), get_user(), ...).
1914 config FAIL_MAKE_REQUEST
1915 bool "Fault-injection capability for disk IO"
1916 depends on FAULT_INJECTION && BLOCK
1918 Provide fault-injection capability for disk IO.
1920 config FAIL_IO_TIMEOUT
1921 bool "Fault-injection capability for faking disk interrupts"
1922 depends on FAULT_INJECTION && BLOCK
1924 Provide fault-injection capability on end IO handling. This
1925 will make the block layer "forget" an interrupt as configured,
1926 thus exercising the error handling.
1928 Only works with drivers that use the generic timeout handling,
1929 for others it wont do anything.
1932 bool "Fault-injection capability for futexes"
1934 depends on FAULT_INJECTION && FUTEX
1936 Provide fault-injection capability for futexes.
1938 config FAULT_INJECTION_DEBUG_FS
1939 bool "Debugfs entries for fault-injection capabilities"
1940 depends on FAULT_INJECTION && SYSFS && DEBUG_FS
1942 Enable configuration of fault-injection capabilities via debugfs.
1944 config FAIL_FUNCTION
1945 bool "Fault-injection capability for functions"
1946 depends on FAULT_INJECTION_DEBUG_FS && FUNCTION_ERROR_INJECTION
1948 Provide function-based fault-injection capability.
1949 This will allow you to override a specific function with a return
1950 with given return value. As a result, function caller will see
1951 an error value and have to handle it. This is useful to test the
1952 error handling in various subsystems.
1954 config FAIL_MMC_REQUEST
1955 bool "Fault-injection capability for MMC IO"
1956 depends on FAULT_INJECTION_DEBUG_FS && MMC
1958 Provide fault-injection capability for MMC IO.
1959 This will make the mmc core return data errors. This is
1960 useful to test the error handling in the mmc block device
1961 and to test how the mmc host driver handles retries from
1964 config FAULT_INJECTION_STACKTRACE_FILTER
1965 bool "stacktrace filter for fault-injection capabilities"
1966 depends on FAULT_INJECTION_DEBUG_FS && STACKTRACE_SUPPORT
1969 depends on FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
1971 Provide stacktrace filter for fault-injection capabilities
1973 config ARCH_HAS_KCOV
1976 An architecture should select this when it can successfully
1977 build and run with CONFIG_KCOV. This typically requires
1978 disabling instrumentation for some early boot code.
1980 config CC_HAS_SANCOV_TRACE_PC
1981 def_bool $(cc-option,-fsanitize-coverage=trace-pc)
1985 bool "Code coverage for fuzzing"
1986 depends on ARCH_HAS_KCOV
1987 depends on CC_HAS_SANCOV_TRACE_PC || GCC_PLUGINS
1989 select GCC_PLUGIN_SANCOV if !CC_HAS_SANCOV_TRACE_PC
1991 KCOV exposes kernel code coverage information in a form suitable
1992 for coverage-guided fuzzing (randomized testing).
1994 If RANDOMIZE_BASE is enabled, PC values will not be stable across
1995 different machines and across reboots. If you need stable PC values,
1996 disable RANDOMIZE_BASE.
1998 For more details, see Documentation/dev-tools/kcov.rst.
2000 config KCOV_ENABLE_COMPARISONS
2001 bool "Enable comparison operands collection by KCOV"
2003 depends on $(cc-option,-fsanitize-coverage=trace-cmp)
2005 KCOV also exposes operands of every comparison in the instrumented
2006 code along with operand sizes and PCs of the comparison instructions.
2007 These operands can be used by fuzzing engines to improve the quality
2008 of fuzzing coverage.
2010 config KCOV_INSTRUMENT_ALL
2011 bool "Instrument all code by default"
2015 If you are doing generic system call fuzzing (like e.g. syzkaller),
2016 then you will want to instrument the whole kernel and you should
2017 say y here. If you are doing more targeted fuzzing (like e.g.
2018 filesystem fuzzing with AFL) then you will want to enable coverage
2019 for more specific subsets of files, and should say n here.
2021 config KCOV_IRQ_AREA_SIZE
2022 hex "Size of interrupt coverage collection area in words"
2026 KCOV uses preallocated per-cpu areas to collect coverage from
2027 soft interrupts. This specifies the size of those areas in the
2028 number of unsigned long words.
2030 menuconfig RUNTIME_TESTING_MENU
2031 bool "Runtime Testing"
2034 if RUNTIME_TESTING_MENU
2037 tristate "Linux Kernel Dump Test Tool Module"
2040 This module enables testing of the different dumping mechanisms by
2041 inducing system failures at predefined crash points.
2042 If you don't need it: say N
2043 Choose M here to compile this code as a module. The module will be
2046 Documentation on how to use the module can be found in
2047 Documentation/fault-injection/provoke-crashes.rst
2049 config TEST_LIST_SORT
2050 tristate "Linked list sorting test"
2051 depends on DEBUG_KERNEL || m
2053 Enable this to turn on 'list_sort()' function test. This test is
2054 executed only once during system boot (so affects only boot time),
2055 or at module load time.
2059 config TEST_MIN_HEAP
2060 tristate "Min heap test"
2061 depends on DEBUG_KERNEL || m
2063 Enable this to turn on min heap function tests. This test is
2064 executed only once during system boot (so affects only boot time),
2065 or at module load time.
2070 tristate "Array-based sort test"
2071 depends on DEBUG_KERNEL || m
2073 This option enables the self-test function of 'sort()' at boot,
2074 or at module load time.
2079 tristate "64bit/32bit division and modulo test"
2080 depends on DEBUG_KERNEL || m
2082 Enable this to turn on 'do_div()' function test. This test is
2083 executed only once during system boot (so affects only boot time),
2084 or at module load time.
2088 config KPROBES_SANITY_TEST
2089 bool "Kprobes sanity tests"
2090 depends on DEBUG_KERNEL
2093 This option provides for testing basic kprobes functionality on
2094 boot. Samples of kprobe and kretprobe are inserted and
2095 verified for functionality.
2097 Say N if you are unsure.
2099 config BACKTRACE_SELF_TEST
2100 tristate "Self test for the backtrace code"
2101 depends on DEBUG_KERNEL
2103 This option provides a kernel module that can be used to test
2104 the kernel stack backtrace code. This option is not useful
2105 for distributions or general kernels, but only for kernel
2106 developers working on architecture code.
2108 Note that if you want to also test saved backtraces, you will
2109 have to enable STACKTRACE as well.
2111 Say N if you are unsure.
2114 tristate "Red-Black tree test"
2115 depends on DEBUG_KERNEL
2117 A benchmark measuring the performance of the rbtree library.
2118 Also includes rbtree invariant checks.
2120 config REED_SOLOMON_TEST
2121 tristate "Reed-Solomon library test"
2122 depends on DEBUG_KERNEL || m
2124 select REED_SOLOMON_ENC16
2125 select REED_SOLOMON_DEC16
2127 This option enables the self-test function of rslib at boot,
2128 or at module load time.
2132 config INTERVAL_TREE_TEST
2133 tristate "Interval tree test"
2134 depends on DEBUG_KERNEL
2135 select INTERVAL_TREE
2137 A benchmark measuring the performance of the interval tree library
2140 tristate "Per cpu operations test"
2141 depends on m && DEBUG_KERNEL
2143 Enable this option to build test module which validates per-cpu
2148 config ATOMIC64_SELFTEST
2149 tristate "Perform an atomic64_t self-test"
2151 Enable this option to test the atomic64_t functions at boot or
2152 at module load time.
2156 config ASYNC_RAID6_TEST
2157 tristate "Self test for hardware accelerated raid6 recovery"
2158 depends on ASYNC_RAID6_RECOV
2161 This is a one-shot self test that permutes through the
2162 recovery of all the possible two disk failure scenarios for a
2163 N-disk array. Recovery is performed with the asynchronous
2164 raid6 recovery routines, and will optionally use an offload
2165 engine if one is available.
2170 tristate "Test functions located in the hexdump module at runtime"
2172 config TEST_STRING_HELPERS
2173 tristate "Test functions located in the string_helpers module at runtime"
2176 tristate "Test strscpy*() family of functions at runtime"
2179 tristate "Test kstrto*() family of functions at runtime"
2182 tristate "Test printf() family of functions at runtime"
2185 tristate "Test bitmap_*() family of functions at runtime"
2187 Enable this option to test the bitmap functions at boot.
2192 tristate "Test functions located in the uuid module at runtime"
2195 tristate "Test the XArray code at runtime"
2197 config TEST_OVERFLOW
2198 tristate "Test check_*_overflow() functions at runtime"
2200 config TEST_RHASHTABLE
2201 tristate "Perform selftest on resizable hash table"
2203 Enable this option to test the rhashtable functions at boot.
2208 tristate "Perform selftest on hash functions"
2210 Enable this option to test the kernel's integer (<linux/hash.h>),
2211 string (<linux/stringhash.h>), and siphash (<linux/siphash.h>)
2212 hash functions on boot (or module load).
2214 This is intended to help people writing architecture-specific
2215 optimized versions. If unsure, say N.
2218 tristate "Perform selftest on IDA functions"
2221 tristate "Perform selftest on priority array manager"
2224 Enable this option to test priority array manager on boot
2229 config TEST_IRQ_TIMINGS
2230 bool "IRQ timings selftest"
2231 depends on IRQ_TIMINGS
2233 Enable this option to test the irq timings code on boot.
2238 tristate "Test module loading with 'hello world' module"
2241 This builds the "test_module" module that emits "Hello, world"
2242 on printk when loaded. It is designed to be used for basic
2243 evaluation of the module loading subsystem (for example when
2244 validating module verification). It lacks any extra dependencies,
2245 and will not normally be loaded by the system unless explicitly
2251 tristate "Test module for compilation of bitops operations"
2254 This builds the "test_bitops" module that is much like the
2255 TEST_LKM module except that it does a basic exercise of the
2256 set/clear_bit macros and get_count_order/long to make sure there are
2257 no compiler warnings from C=1 sparse checker or -Wextra
2258 compilations. It has no dependencies and doesn't run or load unless
2259 explicitly requested by name. for example: modprobe test_bitops.
2264 tristate "Test module for stress/performance analysis of vmalloc allocator"
2269 This builds the "test_vmalloc" module that should be used for
2270 stress and performance analysis. So, any new change for vmalloc
2271 subsystem can be evaluated from performance and stability point
2276 config TEST_USER_COPY
2277 tristate "Test user/kernel boundary protections"
2280 This builds the "test_user_copy" module that runs sanity checks
2281 on the copy_to/from_user infrastructure, making sure basic
2282 user/kernel boundary testing is working. If it fails to load,
2283 a regression has been detected in the user/kernel memory boundary
2289 tristate "Test BPF filter functionality"
2292 This builds the "test_bpf" module that runs various test vectors
2293 against the BPF interpreter or BPF JIT compiler depending on the
2294 current setting. This is in particular useful for BPF JIT compiler
2295 development, but also to run regression tests against changes in
2296 the interpreter code. It also enables test stubs for eBPF maps and
2297 verifier used by user space verifier testsuite.
2301 config TEST_BLACKHOLE_DEV
2302 tristate "Test blackhole netdev functionality"
2305 This builds the "test_blackhole_dev" module that validates the
2306 data path through this blackhole netdev.
2310 config FIND_BIT_BENCHMARK
2311 tristate "Test find_bit functions"
2313 This builds the "test_find_bit" module that measure find_*_bit()
2314 functions performance.
2318 config TEST_FIRMWARE
2319 tristate "Test firmware loading via userspace interface"
2320 depends on FW_LOADER
2322 This builds the "test_firmware" module that creates a userspace
2323 interface for testing firmware loading. This can be used to
2324 control the triggering of firmware loading without needing an
2325 actual firmware-using device. The contents can be rechecked by
2331 tristate "sysctl test driver"
2332 depends on PROC_SYSCTL
2334 This builds the "test_sysctl" module. This driver enables to test the
2335 proc sysctl interfaces available to drivers safely without affecting
2336 production knobs which might alter system functionality.
2340 config BITFIELD_KUNIT
2341 tristate "KUnit test bitfield functions at runtime"
2344 Enable this option to test the bitfield functions at boot.
2346 KUnit tests run during boot and output the results to the debug log
2347 in TAP format (http://testanything.org/). Only useful for kernel devs
2348 running the KUnit test harness, and not intended for inclusion into a
2351 For more information on KUnit and unit tests in general please refer
2352 to the KUnit documentation in Documentation/dev-tools/kunit/.
2356 config RESOURCE_KUNIT_TEST
2357 tristate "KUnit test for resource API"
2360 This builds the resource API unit test.
2361 Tests the logic of API provided by resource.c and ioport.h.
2362 For more information on KUnit and unit tests in general please refer
2363 to the KUnit documentation in Documentation/dev-tools/kunit/.
2367 config SYSCTL_KUNIT_TEST
2368 tristate "KUnit test for sysctl" if !KUNIT_ALL_TESTS
2370 default KUNIT_ALL_TESTS
2372 This builds the proc sysctl unit test, which runs on boot.
2373 Tests the API contract and implementation correctness of sysctl.
2374 For more information on KUnit and unit tests in general please refer
2375 to the KUnit documentation in Documentation/dev-tools/kunit/.
2379 config LIST_KUNIT_TEST
2380 tristate "KUnit Test for Kernel Linked-list structures" if !KUNIT_ALL_TESTS
2382 default KUNIT_ALL_TESTS
2384 This builds the linked list KUnit test suite.
2385 It tests that the API and basic functionality of the list_head type
2386 and associated macros.
2388 KUnit tests run during boot and output the results to the debug log
2389 in TAP format (https://testanything.org/). Only useful for kernel devs
2390 running the KUnit test harness, and not intended for inclusion into a
2393 For more information on KUnit and unit tests in general please refer
2394 to the KUnit documentation in Documentation/dev-tools/kunit/.
2398 config LINEAR_RANGES_TEST
2399 tristate "KUnit test for linear_ranges"
2401 select LINEAR_RANGES
2403 This builds the linear_ranges unit test, which runs on boot.
2404 Tests the linear_ranges logic correctness.
2405 For more information on KUnit and unit tests in general please refer
2406 to the KUnit documentation in Documentation/dev-tools/kunit/.
2410 config CMDLINE_KUNIT_TEST
2411 tristate "KUnit test for cmdline API"
2414 This builds the cmdline API unit test.
2415 Tests the logic of API provided by cmdline.c.
2416 For more information on KUnit and unit tests in general please refer
2417 to the KUnit documentation in Documentation/dev-tools/kunit/.
2422 tristate "KUnit test for bits.h"
2425 This builds the bits unit test.
2426 Tests the logic of macros defined in bits.h.
2427 For more information on KUnit and unit tests in general please refer
2428 to the KUnit documentation in Documentation/dev-tools/kunit/.
2433 tristate "udelay test driver"
2435 This builds the "udelay_test" module that helps to make sure
2436 that udelay() is working properly.
2440 config TEST_STATIC_KEYS
2441 tristate "Test static keys"
2444 Test the static key interfaces.
2449 tristate "kmod stress tester"
2451 depends on NETDEVICES && NET_CORE && INET # for TUN
2458 Test the kernel's module loading mechanism: kmod. kmod implements
2459 support to load modules using the Linux kernel's usermode helper.
2460 This test provides a series of tests against kmod.
2462 Although technically you can either build test_kmod as a module or
2463 into the kernel we disallow building it into the kernel since
2464 it stress tests request_module() and this will very likely cause
2465 some issues by taking over precious threads available from other
2466 module load requests, ultimately this could be fatal.
2470 tools/testing/selftests/kmod/kmod.sh --help
2474 config TEST_DEBUG_VIRTUAL
2475 tristate "Test CONFIG_DEBUG_VIRTUAL feature"
2476 depends on DEBUG_VIRTUAL
2478 Test the kernel's ability to detect incorrect calls to
2479 virt_to_phys() done against the non-linear part of the
2480 kernel's virtual address map.
2484 config TEST_MEMCAT_P
2485 tristate "Test memcat_p() helper function"
2487 Test the memcat_p() helper for correctly merging two
2488 pointer arrays together.
2492 config TEST_LIVEPATCH
2493 tristate "Test livepatching"
2495 depends on DYNAMIC_DEBUG
2496 depends on LIVEPATCH
2499 Test kernel livepatching features for correctness. The tests will
2500 load test modules that will be livepatched in various scenarios.
2502 To run all the livepatching tests:
2504 make -C tools/testing/selftests TARGETS=livepatch run_tests
2506 Alternatively, individual tests may be invoked:
2508 tools/testing/selftests/livepatch/test-callbacks.sh
2509 tools/testing/selftests/livepatch/test-livepatch.sh
2510 tools/testing/selftests/livepatch/test-shadow-vars.sh
2515 tristate "Perform selftest on object aggreration manager"
2519 Enable this option to test object aggregation manager on boot
2523 config TEST_STACKINIT
2524 tristate "Test level of stack variable initialization"
2526 Test if the kernel is zero-initializing stack variables and
2527 padding. Coverage is controlled by compiler flags,
2528 CONFIG_GCC_PLUGIN_STRUCTLEAK, CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF,
2529 or CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL.
2534 tristate "Test heap/page initialization"
2536 Test if the kernel is zero-initializing heap and page allocations.
2537 This can be useful to test init_on_alloc and init_on_free features.
2542 tristate "Test HMM (Heterogeneous Memory Management)"
2543 depends on TRANSPARENT_HUGEPAGE
2544 depends on DEVICE_PRIVATE
2548 This is a pseudo device driver solely for testing HMM.
2549 Say M here if you want to build the HMM test module.
2550 Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.
2554 config TEST_FREE_PAGES
2555 tristate "Test freeing pages"
2557 Test that a memory leak does not occur due to a race between
2558 freeing a block of pages and a speculative page reference.
2559 Loading this module is safe if your kernel has the bug fixed.
2560 If the bug is not fixed, it will leak gigabytes of memory and
2561 probably OOM your system.
2564 tristate "Test floating point operations in kernel space"
2565 depends on X86 && !KCOV_INSTRUMENT_ALL
2567 Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
2568 which will trigger a sequence of floating point operations. This is used
2569 for self-testing floating point control register setting in
2574 endif # RUNTIME_TESTING_MENU
2576 config ARCH_USE_MEMTEST
2579 An architecture should select this when it uses early_memtest()
2580 during boot process.
2584 depends on ARCH_USE_MEMTEST
2586 This option adds a kernel parameter 'memtest', which allows memtest
2587 to be set and executed.
2588 memtest=0, mean disabled; -- default
2589 memtest=1, mean do 1 test pattern;
2591 memtest=17, mean do 17 test patterns.
2592 If you are unsure how to answer this question, answer N.
2596 config HYPERV_TESTING
2597 bool "Microsoft Hyper-V driver testing"
2599 depends on HYPERV && DEBUG_FS
2601 Select this option to enable Hyper-V vmbus testing.
2603 endmenu # "Kernel Testing and Coverage"
2605 source "Documentation/Kconfig"
2607 endmenu # Kernel hacking
projects / platform / kernel / linux-rpi.git / blob