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