| Kconfig.debug (42e405f7b1d252c90a2468dd2140f47b8142b7a0) | Kconfig.debug (5c9a8750a6409c63a0f01d51a9024861022f6593) |
|---|---|
| 1menu "printk and dmesg options" 2 3config PRINTK_TIME 4 bool "Show timing information on printks" 5 depends on PRINTK 6 help 7 Selecting this option causes time stamps of the printk() 8 messages to be added to the output of the syslog() system --- 328 unchanged lines hidden (view full) --- 337 AVR32 || SUPERH || BLACKFIN || MN10300 || METAG) || \ 338 ARCH_WANT_FRAME_POINTERS 339 default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS 340 help 341 If you say Y here the resulting kernel image will be slightly 342 larger and slower, but it gives very useful debugging information 343 in case of kernel bugs. (precise oopses/stacktraces/warnings) 344 | 1menu "printk and dmesg options" 2 3config PRINTK_TIME 4 bool "Show timing information on printks" 5 depends on PRINTK 6 help 7 Selecting this option causes time stamps of the printk() 8 messages to be added to the output of the syslog() system --- 328 unchanged lines hidden (view full) --- 337 AVR32 || SUPERH || BLACKFIN || MN10300 || METAG) || \ 338 ARCH_WANT_FRAME_POINTERS 339 default y if (DEBUG_INFO && UML) || ARCH_WANT_FRAME_POINTERS 340 help 341 If you say Y here the resulting kernel image will be slightly 342 larger and slower, but it gives very useful debugging information 343 in case of kernel bugs. (precise oopses/stacktraces/warnings) 344 |
| 345config STACK_VALIDATION 346 bool "Compile-time stack metadata validation" 347 depends on HAVE_STACK_VALIDATION 348 default n 349 help 350 Add compile-time checks to validate stack metadata, including frame 351 pointers (if CONFIG_FRAME_POINTER is enabled). This helps ensure 352 that runtime stack traces are more reliable. 353 354 For more information, see 355 tools/objtool/Documentation/stack-validation.txt. 356 |
|
| 345config DEBUG_FORCE_WEAK_PER_CPU 346 bool "Force weak per-cpu definitions" 347 depends on DEBUG_KERNEL 348 help 349 s390 and alpha require percpu variables in modules to be 350 defined weak to work around addressing range issue which 351 puts the following two restrictions on percpu variable 352 definitions. --- 326 unchanged lines hidden (view full) --- 679 If in doubt, say "N". 680 681source "lib/Kconfig.kmemcheck" 682 683source "lib/Kconfig.kasan" 684 685endmenu # "Memory Debugging" 686 | 357config DEBUG_FORCE_WEAK_PER_CPU 358 bool "Force weak per-cpu definitions" 359 depends on DEBUG_KERNEL 360 help 361 s390 and alpha require percpu variables in modules to be 362 defined weak to work around addressing range issue which 363 puts the following two restrictions on percpu variable 364 definitions. --- 326 unchanged lines hidden (view full) --- 691 If in doubt, say "N". 692 693source "lib/Kconfig.kmemcheck" 694 695source "lib/Kconfig.kasan" 696 697endmenu # "Memory Debugging" 698 |
| 699config ARCH_HAS_KCOV 700 bool 701 help 702 KCOV does not have any arch-specific code, but currently it is enabled 703 only for x86_64. KCOV requires testing on other archs, and most likely 704 disabling of instrumentation for some early boot code. 705 706config KCOV 707 bool "Code coverage for fuzzing" 708 depends on ARCH_HAS_KCOV 709 select DEBUG_FS 710 help 711 KCOV exposes kernel code coverage information in a form suitable 712 for coverage-guided fuzzing (randomized testing). 713 714 If RANDOMIZE_BASE is enabled, PC values will not be stable across 715 different machines and across reboots. If you need stable PC values, 716 disable RANDOMIZE_BASE. 717 718 For more details, see Documentation/kcov.txt. 719 |
|
| 687config DEBUG_SHIRQ 688 bool "Debug shared IRQ handlers" 689 depends on DEBUG_KERNEL 690 help 691 Enable this to generate a spurious interrupt as soon as a shared 692 interrupt handler is registered, and just before one is deregistered. 693 Drivers ought to be able to handle interrupts coming in at those 694 points; some don't and need to be caught. --- 1066 unchanged lines hidden (view full) --- 1761 tristate "Test functions located in the string_helpers module at runtime" 1762 1763config TEST_KSTRTOX 1764 tristate "Test kstrto*() family of functions at runtime" 1765 1766config TEST_PRINTF 1767 tristate "Test printf() family of functions at runtime" 1768 | 720config DEBUG_SHIRQ 721 bool "Debug shared IRQ handlers" 722 depends on DEBUG_KERNEL 723 help 724 Enable this to generate a spurious interrupt as soon as a shared 725 interrupt handler is registered, and just before one is deregistered. 726 Drivers ought to be able to handle interrupts coming in at those 727 points; some don't and need to be caught. --- 1066 unchanged lines hidden (view full) --- 1794 tristate "Test functions located in the string_helpers module at runtime" 1795 1796config TEST_KSTRTOX 1797 tristate "Test kstrto*() family of functions at runtime" 1798 1799config TEST_PRINTF 1800 tristate "Test printf() family of functions at runtime" 1801 |
| 1802config TEST_BITMAP 1803 tristate "Test bitmap_*() family of functions at runtime" 1804 default n 1805 help 1806 Enable this option to test the bitmap functions at boot. 1807 1808 If unsure, say N. 1809 |
|
| 1769config TEST_RHASHTABLE 1770 tristate "Perform selftest on resizable hash table" 1771 default n 1772 help 1773 Enable this option to test the rhashtable functions at boot. 1774 1775 If unsure, say N. 1776 --- 187 unchanged lines hidden --- | 1810config TEST_RHASHTABLE 1811 tristate "Perform selftest on resizable hash table" 1812 default n 1813 help 1814 Enable this option to test the rhashtable functions at boot. 1815 1816 If unsure, say N. 1817 --- 187 unchanged lines hidden --- |