diff options
Diffstat (limited to 'lib/Kconfig.debug')
-rw-r--r-- | lib/Kconfig.debug | 52 |
1 files changed, 52 insertions, 0 deletions
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index c4ecb2994ba3..89f4035b526c 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug | |||
@@ -494,6 +494,30 @@ config RCU_TORTURE_TEST | |||
494 | Say M if you want the RCU torture tests to build as a module. | 494 | Say M if you want the RCU torture tests to build as a module. |
495 | Say N if you are unsure. | 495 | Say N if you are unsure. |
496 | 496 | ||
497 | config KPROBES_SANITY_TEST | ||
498 | bool "Kprobes sanity tests" | ||
499 | depends on DEBUG_KERNEL | ||
500 | depends on KPROBES | ||
501 | default n | ||
502 | help | ||
503 | This option provides for testing basic kprobes functionality on | ||
504 | boot. A sample kprobe, jprobe and kretprobe are inserted and | ||
505 | verified for functionality. | ||
506 | |||
507 | Say N if you are unsure. | ||
508 | |||
509 | config BACKTRACE_SELF_TEST | ||
510 | tristate "Self test for the backtrace code" | ||
511 | depends on DEBUG_KERNEL | ||
512 | default n | ||
513 | help | ||
514 | This option provides a kernel module that can be used to test | ||
515 | the kernel stack backtrace code. This option is not useful | ||
516 | for distributions or general kernels, but only for kernel | ||
517 | developers working on architecture code. | ||
518 | |||
519 | Say N if you are unsure. | ||
520 | |||
497 | config LKDTM | 521 | config LKDTM |
498 | tristate "Linux Kernel Dump Test Tool Module" | 522 | tristate "Linux Kernel Dump Test Tool Module" |
499 | depends on DEBUG_KERNEL | 523 | depends on DEBUG_KERNEL |
@@ -562,5 +586,33 @@ config LATENCYTOP | |||
562 | Enable this option if you want to use the LatencyTOP tool | 586 | Enable this option if you want to use the LatencyTOP tool |
563 | to find out which userspace is blocking on what kernel operations. | 587 | to find out which userspace is blocking on what kernel operations. |
564 | 588 | ||
589 | config PROVIDE_OHCI1394_DMA_INIT | ||
590 | bool "Provide code for enabling DMA over FireWire early on boot" | ||
591 | depends on PCI && X86 | ||
592 | help | ||
593 | If you want to debug problems which hang or crash the kernel early | ||
594 | on boot and the crashing machine has a FireWire port, you can use | ||
595 | this feature to remotely access the memory of the crashed machine | ||
596 | over FireWire. This employs remote DMA as part of the OHCI1394 | ||
597 | specification which is now the standard for FireWire controllers. | ||
598 | |||
599 | With remote DMA, you can monitor the printk buffer remotely using | ||
600 | firescope and access all memory below 4GB using fireproxy from gdb. | ||
601 | Even controlling a kernel debugger is possible using remote DMA. | ||
602 | |||
603 | Usage: | ||
604 | |||
605 | If ohci1394_dma=early is used as boot parameter, it will initialize | ||
606 | all OHCI1394 controllers which are found in the PCI config space. | ||
607 | |||
608 | As all changes to the FireWire bus such as enabling and disabling | ||
609 | devices cause a bus reset and thereby disable remote DMA for all | ||
610 | devices, be sure to have the cable plugged and FireWire enabled on | ||
611 | the debugging host before booting the debug target for debugging. | ||
612 | |||
613 | This code (~1k) is freed after boot. By then, the firewire stack | ||
614 | in charge of the OHCI-1394 controllers should be used instead. | ||
615 | |||
616 | See Documentation/debugging-via-ohci1394.txt for more information. | ||
565 | 617 | ||
566 | source "samples/Kconfig" | 618 | source "samples/Kconfig" |