Kconfig.debug (a35762dd14adb952442e487d8dad4bb50b614b2b) Kconfig.debug (aebc7b0d8d91bbc69e976909963046bc48bca4fd)
1# SPDX-License-Identifier: GPL-2.0-only
2menu "Kernel hacking"
3
4menu "printk and dmesg options"
5
6config PRINTK_TIME
7 bool "Show timing information on printks"
8 depends on PRINTK

--- 1186 unchanged lines hidden (view full) ---

1195 "workqueue.watchdog_thresh" and its sysfs counterpart.
1196
1197config WQ_CPU_INTENSIVE_REPORT
1198 bool "Report per-cpu work items which hog CPU for too long"
1199 depends on DEBUG_KERNEL
1200 help
1201 Say Y here to enable reporting of concurrency-managed per-cpu work
1202 items that hog CPUs for longer than
1# SPDX-License-Identifier: GPL-2.0-only
2menu "Kernel hacking"
3
4menu "printk and dmesg options"
5
6config PRINTK_TIME
7 bool "Show timing information on printks"
8 depends on PRINTK

--- 1186 unchanged lines hidden (view full) ---

1195 "workqueue.watchdog_thresh" and its sysfs counterpart.
1196
1197config WQ_CPU_INTENSIVE_REPORT
1198 bool "Report per-cpu work items which hog CPU for too long"
1199 depends on DEBUG_KERNEL
1200 help
1201 Say Y here to enable reporting of concurrency-managed per-cpu work
1202 items that hog CPUs for longer than
1203 workqueue.cpu_intensive_thresh_us. Workqueue automatically
1203 workqueue.cpu_intensive_threshold_us. Workqueue automatically
1204 detects and excludes them from concurrency management to prevent
1205 them from stalling other per-cpu work items. Occassional
1206 triggering may not necessarily indicate a problem. Repeated
1207 triggering likely indicates that the work item should be switched
1208 to use an unbound workqueue.
1209
1210config TEST_LOCKUP
1211 tristate "Test module to generate lockups"

--- 457 unchanged lines hidden (view full) ---

1669config HAVE_DEBUG_BUGVERBOSE
1670 bool
1671
1672menu "Debug kernel data structures"
1673
1674config DEBUG_LIST
1675 bool "Debug linked list manipulation"
1676 depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION
1204 detects and excludes them from concurrency management to prevent
1205 them from stalling other per-cpu work items. Occassional
1206 triggering may not necessarily indicate a problem. Repeated
1207 triggering likely indicates that the work item should be switched
1208 to use an unbound workqueue.
1209
1210config TEST_LOCKUP
1211 tristate "Test module to generate lockups"

--- 457 unchanged lines hidden (view full) ---

1669config HAVE_DEBUG_BUGVERBOSE
1670 bool
1671
1672menu "Debug kernel data structures"
1673
1674config DEBUG_LIST
1675 bool "Debug linked list manipulation"
1676 depends on DEBUG_KERNEL || BUG_ON_DATA_CORRUPTION
1677 select LIST_HARDENED
1677 help
1678 help
1678 Enable this to turn on extended checks in the linked-list
1679 walking routines.
1679 Enable this to turn on extended checks in the linked-list walking
1680 routines.
1680
1681
1682 This option trades better quality error reports for performance, and
1683 is more suitable for kernel debugging. If you care about performance,
1684 you should only enable CONFIG_LIST_HARDENED instead.
1685
1681 If unsure, say N.
1682
1683config DEBUG_PLIST
1684 bool "Debug priority linked list manipulation"
1685 depends on DEBUG_KERNEL
1686 help
1687 Enable this to turn on extended checks in the priority-ordered
1688 linked-list (plist) walking routines. This checks the entire

--- 1327 unchanged lines hidden ---
1686 If unsure, say N.
1687
1688config DEBUG_PLIST
1689 bool "Debug priority linked list manipulation"
1690 depends on DEBUG_KERNEL
1691 help
1692 Enable this to turn on extended checks in the priority-ordered
1693 linked-list (plist) walking routines. This checks the entire

--- 1327 unchanged lines hidden ---