ia64/linux-2.6.18-xen.hg

annotate arch/cris/Kconfig.debug @ 673:3161879fdf22

[IA64] xencomm: support XENMEM_add_to_physmap and XENMEM_remove_from_phsymap

support XENMEM_add_to_physmap and XENMEM_remove_from_phsymap.

Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
author Isaku Yamahata <yamahata@valinux.co.jp>
date Tue Sep 16 21:26:15 2008 +0900 (2008-09-16)
parents 831230e53067
children
rev   line source
ian@0 1 menu "Kernel hacking"
ian@0 2
ian@0 3 #bool 'Debug kmalloc/kfree' CONFIG_DEBUG_MALLOC
ian@0 4 config PROFILING
ian@0 5 bool "Kernel profiling support"
ian@0 6
ian@0 7 config SYSTEM_PROFILER
ian@0 8 bool "System profiling support"
ian@0 9
ian@0 10 source "lib/Kconfig.debug"
ian@0 11
ian@0 12 config ETRAX_KGDB
ian@0 13 bool "Use kernel GDB debugger"
ian@0 14 depends on DEBUG_KERNEL
ian@0 15 ---help---
ian@0 16 The CRIS version of gdb can be used to remotely debug a running
ian@0 17 Linux kernel via the serial debug port. Provided you have gdb-cris
ian@0 18 installed, run gdb-cris vmlinux, then type
ian@0 19
ian@0 20 (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
ian@0 21 (gdb) target remote /dev/ttyS0 <- maybe you use another port
ian@0 22
ian@0 23 This should connect you to your booted kernel (or boot it now if you
ian@0 24 didn't before). The kernel halts when it boots, waiting for gdb if
ian@0 25 this option is turned on!
ian@0 26
ian@0 27
ian@0 28 config DEBUG_NMI_OOPS
ian@0 29 bool "NMI causes oops printout"
ian@0 30 depends on DEBUG_KERNEL
ian@0 31 help
ian@0 32 If the system locks up without any debug information you can say Y
ian@0 33 here to make it possible to dump an OOPS with an external NMI.
ian@0 34
ian@0 35 endmenu