blob: fcb06a50fdd2c6e7b05b57704c4ad504e98b40cc [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001menu "Kernel hacking"
2
3source "lib/Kconfig.debug"
4
Linus Torvalds1da177e2005-04-16 15:20:36 -07005config INIT_DEBUG
6 bool "Debug __init statements"
7 depends on DEBUG_KERNEL
8 help
9 Fill __init and __initdata at the end of boot. This helps debugging
10 illegal uses of __init and __initdata after initialization.
11
Arjan van de Ven67df1972006-01-06 00:12:04 -080012config DEBUG_RODATA
13 bool "Write protect kernel read-only data structures"
14 depends on DEBUG_KERNEL
15 help
16 Mark the kernel read-only data as write-protected in the pagetables,
17 in order to catch accidental (and incorrect) writes to such const data.
18 This option may have a slight performance impact because a portion
19 of the kernel code won't be covered by a 2MB TLB anymore.
20 If in doubt, say "N".
21
Linus Torvalds1da177e2005-04-16 15:20:36 -070022config IOMMU_DEBUG
23 depends on GART_IOMMU && DEBUG_KERNEL
24 bool "Enable IOMMU debugging"
25 help
26 Force the IOMMU to on even when you have less than 4GB of
27 memory and add debugging code. On overflow always panic. And
28 allow to enable IOMMU leak tracing. Can be disabled at boot
29 time with iommu=noforce. This will also enable scatter gather
30 list merging. Currently not recommended for production
31 code. When you use it make sure you have a big enough
32 IOMMU/AGP aperture. Most of the options enabled by this can
33 be set more finegrained using the iommu= command line
34 options. See Documentation/x86_64/boot-options.txt for more
35 details.
36
Linus Torvalds1da177e2005-04-16 15:20:36 -070037config IOMMU_LEAK
38 bool "IOMMU leak tracing"
39 depends on DEBUG_KERNEL
40 depends on IOMMU_DEBUG
41 help
42 Add a simple leak tracer to the IOMMU code. This is useful when you
43 are debugging a buggy device driver that leaks IOMMU mappings.
44
45#config X86_REMOTE_DEBUG
46# bool "kgdb debugging stub"
47
48endmenu