Lines Matching full:debugging

130 	  Dynamic debugging is controlled via the 'dynamic_debug/control' file,
207 debugging but costs about 70-100K of memory.
212 bool "Kernel debugging"
245 that will include debugging info resulting in a larger kernel image.
256 Do not build the kernel with debugging information, which will
306 bool "Reduce debugging information"
308 If you say Y here gcc is instructed to generate less debugging
310 need full debugging information (like kgdb or systemtap) won't
311 be happy. But if you merely need debugging information to
331 bool "Compress debugging information with zlib"
346 bool "Compress debugging information with zstd"
427 bool "Provide GDB scripts for kernel debugging"
433 instance. See Documentation/dev-tools/gdb-kernel-debugging.rst
539 larger and slower, but it gives very useful debugging information
569 and debugging magic section games, and for seeing which
590 menu "Generic Kernel Debugging Instruments"
597 if the system crashes for example during kernel debugging (e.g., you
639 debugging files into. Enable this option to be able to read and
685 menu "Networking Debugging"
689 endmenu # "Networking Debugging"
691 menu "Memory Debugging"
738 Enable this to turn on debugging of RCU list heads (call_rcu() usage).
757 bool "Enable shrinker debugging support"
820 Enable VM maple tree debugging information and extra validations.
828 Enable VM red-black tree debugging information and extra validations.
942 bool "Highmem debugging"
975 endmenu # "Memory Debugging"
1236 menu "Scheduler Debugging"
1239 bool "Collect scheduler debugging info"
1259 stats may be useful for both tuning and debugging the scheduler
1260 If you aren't debugging the scheduler or trying to tune a specific
1289 depending on workload as it triggers debugging routines for each
1290 this_cpu operation. It should only be used for debugging purposes.
1292 menu "Lock Debugging (spinlocks, mutexes, etc...)"
1300 bool "Lock debugging: prove locking correctness"
1386 bool "RT Mutex debugging, deadlock detection"
1393 bool "Spinlock and rw-lock debugging: basic checks"
1403 bool "Mutex debugging: basic checks"
1410 bool "Wait/wound mutex debugging: Slowpath testing"
1428 bool "RW Semaphore debugging: basic checks"
1431 This debugging feature allows mismatched rw semaphore locks
1435 bool "Lock debugging: detect incorrect freeing of live locks"
1500 bool "Lock dependency engine debugging"
1525 are detected by debugging mechanisms or not. (if you disable
1526 lock debugging then those bugs won't be detected of course.)
1567 bool "Debugging for csd_lock_wait(), called from smp_call_function*()"
1578 bool "Default csd_lock_wait() debugging on at boot time"
1584 default to 1 (basic debugging) instead of 0 (no debugging).
1586 endmenu # lock debugging
1593 either tracing or lock debugging.
1601 bool "Debugging for CPUs failing to respond to backtrace requests"
1624 It is also used by various kernel debugging features that require
1655 bool "kobject debugging"
1658 If you say Y here, some extra kobject debugging messages will be sent
1662 bool "kobject release debugging"
1694 is more suitable for kernel debugging. If you care about performance,
1742 Enable maple tree debugging information and extra validations.
1800 that they can be kprobed for debugging.
1805 bool "Remote debugging over FireWire early on boot"
1826 the debugging host before booting the debug target for debugging.
1831 See Documentation/core-api/debugging-via-ohci1394.rst for more information.
1847 be used by people debugging the kernel. Note that with PAT support
1865 specific access can be used by people debugging kernel drivers.
1874 menu "$(SRCARCH) Debugging"
2674 Tests SLUB cache debugging functionality.
2995 compilation on or off. This can be used to enable extra debugging