3 source "lib/Kconfig.debug"
5 # !SMP for now because the context switch early causes GPF in segment reloading
6 # and the GS base checking does the wrong thing then, causing a hang.
8 bool "Additional run-time checks"
9 depends on DEBUG_KERNEL && !SMP
11 Enables some internal consistency checks for kernel debugging.
12 You should normally say N.
15 bool "Debug __init statements"
16 depends on DEBUG_KERNEL
18 Fill __init and __initdata at the end of boot. This helps debugging
19 illegal uses of __init and __initdata after initialization.
22 bool "Collect scheduler statistics"
23 depends on DEBUG_KERNEL && PROC_FS
25 If you say Y here, additional code will be inserted into the
26 scheduler and related routines to collect statistics about
27 scheduler behavior and provide them in /proc/schedstat. These
28 stats may be useful for both tuning and debugging the scheduler
29 If you aren't debugging the scheduler or trying to tune a specific
30 application, you can say N to avoid the very slight overhead
34 depends on GART_IOMMU && DEBUG_KERNEL
35 bool "Enable IOMMU debugging"
37 Force the IOMMU to on even when you have less than 4GB of
38 memory and add debugging code. On overflow always panic. And
39 allow to enable IOMMU leak tracing. Can be disabled at boot
40 time with iommu=noforce. This will also enable scatter gather
41 list merging. Currently not recommended for production
42 code. When you use it make sure you have a big enough
43 IOMMU/AGP aperture. Most of the options enabled by this can
44 be set more finegrained using the iommu= command line
45 options. See Documentation/x86_64/boot-options.txt for more
49 bool "IOMMU leak tracing"
50 depends on DEBUG_KERNEL
51 depends on IOMMU_DEBUG
53 Add a simple leak tracer to the IOMMU code. This is useful when you
54 are debugging a buggy device driver that leaks IOMMU mappings.
56 #config X86_REMOTE_DEBUG
57 # bool "kgdb debugging stub"