lib: introduce common method to convert hex digits

[safe/jmp/linux-2.6] / lib / Kconfig.debug

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 82fbc49..2312089 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -50,6 +50,14 @@ config MAGIC_SYSRQ
          keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
          unless you really know what this hack does.
 
          keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
          unless you really know what this hack does.
 

+config STRIP_ASM_SYMS
+       bool "Strip assembler-generated symbols during link"
+       default n
+       help
+         Strip internal assembler-generated symbols during a link (symbols
+         that look like '.Lxxx') so they don't pollute the output of
+         get_wchan() and suchlike.
+

 config UNUSED_SYMBOLS
        bool "Enable unused/obsolete exported symbols"
        default y if X86
 config UNUSED_SYMBOLS
        bool "Enable unused/obsolete exported symbols"
        default y if X86


@@ -95,9 +103,10 @@ config HEADERS_CHECK
 
 config DEBUG_SECTION_MISMATCH
        bool "Enable full Section mismatch analysis"
 
 config DEBUG_SECTION_MISMATCH
        bool "Enable full Section mismatch analysis"

-       depends on UNDEFINED
+       depends on UNDEFINED || (BLACKFIN)
+       default y

        # This option is on purpose disabled for now.
        # This option is on purpose disabled for now.

-       # It will be enabled when we are down to a resonable number
+       # It will be enabled when we are down to a reasonable number

        # of section mismatch warnings (< 10 for an allyesconfig build)
        help
          The section mismatch analysis checks if there are illegal
        # of section mismatch warnings (< 10 for an allyesconfig build)
        help
          The section mismatch analysis checks if there are illegal


@@ -290,6 +299,14 @@ config DEBUG_OBJECTS_TIMERS
          timer routines to track the life time of timer objects and
          validate the timer operations.
 
          timer routines to track the life time of timer objects and
          validate the timer operations.
 

+config DEBUG_OBJECTS_WORK
+       bool "Debug work objects"
+       depends on DEBUG_OBJECTS
+       help
+         If you say Y here, additional code will be inserted into the
+         work queue routines to track the life time of work objects and
+         validate the work operations.
+

 config DEBUG_OBJECTS_ENABLE_DEFAULT
        int "debug_objects bootup default value (0-1)"
         range 0 1
 config DEBUG_OBJECTS_ENABLE_DEFAULT
        int "debug_objects bootup default value (0-1)"
         range 0 1


@@ -338,11 +355,13 @@ config SLUB_STATS
 
 config DEBUG_KMEMLEAK
        bool "Kernel memory leak detector"
 
 config DEBUG_KMEMLEAK
        bool "Kernel memory leak detector"

-       depends on DEBUG_KERNEL && EXPERIMENTAL && (X86 || ARM) && \
-               !MEMORY_HOTPLUG
+       depends on DEBUG_KERNEL && EXPERIMENTAL && !MEMORY_HOTPLUG && \
+               (X86 || ARM || PPC || S390 || SPARC64 || SUPERH || MICROBLAZE)
+

        select DEBUG_FS if SYSFS
        select STACKTRACE if STACKTRACE_SUPPORT
        select KALLSYMS
        select DEBUG_FS if SYSFS
        select STACKTRACE if STACKTRACE_SUPPORT
        select KALLSYMS

+       select CRC32

        help
          Say Y here if you want to enable the memory leak
          detector. The memory allocation/freeing is traced in a way
        help
          Say Y here if you want to enable the memory leak
          detector. The memory allocation/freeing is traced in a way


@@ -362,7 +381,7 @@ config DEBUG_KMEMLEAK
 config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
        int "Maximum kmemleak early log entries"
        depends on DEBUG_KMEMLEAK
 config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
        int "Maximum kmemleak early log entries"
        depends on DEBUG_KMEMLEAK

-       range 200 2000
+       range 200 40000

        default 400
        help
          Kmemleak must track all the memory allocations to avoid
        default 400
        help
          Kmemleak must track all the memory allocations to avoid


@@ -383,7 +402,7 @@ config DEBUG_KMEMLEAK_TEST
 
 config DEBUG_PREEMPT
        bool "Debug preemptible kernel"
 
 config DEBUG_PREEMPT
        bool "Debug preemptible kernel"

-       depends on DEBUG_KERNEL && PREEMPT && (TRACE_IRQFLAGS_SUPPORT || PPC64)
+       depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT

        default y
        help
          If you say Y here then the kernel will use a debug variant of the
        default y
        help
          If you say Y here then the kernel will use a debug variant of the


@@ -481,6 +500,30 @@ config PROVE_LOCKING
 
         For more details, see Documentation/lockdep-design.txt.
 
 
         For more details, see Documentation/lockdep-design.txt.
 

+config PROVE_RCU
+       bool "RCU debugging: prove RCU correctness"
+       depends on PROVE_LOCKING
+       default n
+       help
+        This feature enables lockdep extensions that check for correct
+        use of RCU APIs.  This is currently under development.  Say Y
+        if you want to debug RCU usage or help work on the PROVE_RCU
+        feature.
+
+        Say N if you are unsure.
+
+config PROVE_RCU_REPEATEDLY
+       bool "RCU debugging: don't disable PROVE_RCU on first splat"
+       depends on PROVE_RCU
+       default n
+       help
+        By itself, PROVE_RCU will disable checking upon issuing the
+        first warning (or "splat").  This feature prevents such
+        disabling, allowing multiple RCU-lockdep warnings to be printed
+        on a single reboot.
+
+        Say N if you are unsure.
+

 config LOCKDEP
        bool
        depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
 config LOCKDEP
        bool
        depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT


@@ -502,6 +545,14 @@ config LOCK_STAT
 
         For more details, see Documentation/lockstat.txt
 
 
         For more details, see Documentation/lockstat.txt
 

+        This also enables lock events required by "perf lock",
+        subcommand of perf.
+        If you want to use "perf lock", you also need to turn on
+        CONFIG_EVENT_TRACING.
+
+        CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
+        (CONFIG_LOCKDEP defines "acquire" and "release" events.)
+

 config DEBUG_LOCKDEP
        bool "Lock dependency engine debugging"
        depends on DEBUG_KERNEL && LOCKDEP
 config DEBUG_LOCKDEP
        bool "Lock dependency engine debugging"
        depends on DEBUG_KERNEL && LOCKDEP


@@ -558,7 +609,7 @@ config DEBUG_BUGVERBOSE
        depends on BUG
        depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \
                   FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300
        depends on BUG
        depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \
                   FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300

-       default !EMBEDDED
+       default y

        help
          Say Y here to make BUG() panics output the file name and line number
          of the BUG call as well as the EIP and oops trace.  This aids
        help
          Say Y here to make BUG() panics output the file name and line number
          of the BUG call as well as the EIP and oops trace.  This aids


@@ -653,6 +704,21 @@ config DEBUG_NOTIFIERS
          This is a relatively cheap check but if you care about maximum
          performance, say N.
 
          This is a relatively cheap check but if you care about maximum
          performance, say N.
 

+config DEBUG_CREDENTIALS
+       bool "Debug credential management"
+       depends on DEBUG_KERNEL
+       help
+         Enable this to turn on some debug checking for credential
+         management.  The additional code keeps track of the number of
+         pointers from task_structs to any given cred struct, and checks to
+         see that this number never exceeds the usage count of the cred
+         struct.
+
+         Furthermore, if SELinux is enabled, this also checks that the
+         security pointer in the cred struct is never seen to be invalid.
+
+         If unsure, say N.
+

 #
 # Select this config option from the architecture Kconfig, if it
 # it is preferred to always offer frame pointers as a config
 #
 # Select this config option from the architecture Kconfig, if it
 # it is preferred to always offer frame pointers as a config


@@ -726,16 +792,28 @@ config RCU_TORTURE_TEST_RUNNABLE
 config RCU_CPU_STALL_DETECTOR
        bool "Check for stalled CPUs delaying RCU grace periods"
        depends on TREE_RCU || TREE_PREEMPT_RCU
 config RCU_CPU_STALL_DETECTOR
        bool "Check for stalled CPUs delaying RCU grace periods"
        depends on TREE_RCU || TREE_PREEMPT_RCU

-       default n
+       default y

        help
          This option causes RCU to printk information on which
          CPUs are delaying the current grace period, but only when
          the grace period extends for excessive time periods.
 
        help
          This option causes RCU to printk information on which
          CPUs are delaying the current grace period, but only when
          the grace period extends for excessive time periods.
 

-         Say Y if you want RCU to perform such checks.
+         Say N if you want to disable such checks.
+
+         Say Y if you are unsure.
+
+config RCU_CPU_STALL_VERBOSE
+       bool "Print additional per-task information for RCU_CPU_STALL_DETECTOR"
+       depends on RCU_CPU_STALL_DETECTOR && TREE_PREEMPT_RCU
+       default y
+       help
+         This option causes RCU to printk detailed per-task information
+         for any tasks that are stalling the current RCU grace period.

 
          Say N if you are unsure.
 
 
          Say N if you are unsure.
 

+         Say Y if you want to enable such checks.
+

 config KPROBES_SANITY_TEST
        bool "Kprobes sanity tests"
        depends on DEBUG_KERNEL
 config KPROBES_SANITY_TEST
        bool "Kprobes sanity tests"
        depends on DEBUG_KERNEL


@@ -790,10 +868,24 @@ config DEBUG_BLOCK_EXT_DEVT
 
          Say N if you are unsure.
 
 
          Say N if you are unsure.
 

+config DEBUG_FORCE_WEAK_PER_CPU
+       bool "Force weak per-cpu definitions"
+       depends on DEBUG_KERNEL
+       help
+         s390 and alpha require percpu variables in modules to be
+         defined weak to work around addressing range issue which
+         puts the following two restrictions on percpu variable
+         definitions.
+
+         1. percpu symbols must be unique whether static or not
+         2. percpu variables can't be defined inside a function
+
+         To ensure that generic code follows the above rules, this
+         option forces all percpu variables to be defined as weak.
+

 config LKDTM
        tristate "Linux Kernel Dump Test Tool Module"
 config LKDTM
        tristate "Linux Kernel Dump Test Tool Module"

-       depends on DEBUG_KERNEL
-       depends on KPROBES
+       depends on DEBUG_FS

        depends on BLOCK
        default n
        help
        depends on BLOCK
        default n
        help


@@ -804,7 +896,7 @@ config LKDTM
        called lkdtm.
 
        Documentation on how to use the module can be found in
        called lkdtm.
 
        Documentation on how to use the module can be found in

-       drivers/misc/lkdtm.c
+       Documentation/fault-injection/provoke-crashes.txt

 
 config FAULT_INJECTION
        bool "Fault-injection framework"
 
 config FAULT_INJECTION
        bool "Fault-injection framework"


@@ -873,7 +965,7 @@ config LATENCYTOP
 
 config SYSCTL_SYSCALL_CHECK
        bool "Sysctl checks"
 
 config SYSCTL_SYSCALL_CHECK
        bool "Sysctl checks"

-       depends on SYSCTL_SYSCALL
+       depends on SYSCTL

        ---help---
          sys_sysctl uses binary paths that have been found challenging
          to properly maintain and use. This enables checks that help
        ---help---
          sys_sysctl uses binary paths that have been found challenging
          to properly maintain and use. This enables checks that help


@@ -947,10 +1039,10 @@ config DYNAMIC_DEBUG
 
          Usage:
 
 
          Usage:
 

-         Dynamic debugging is controlled via the 'dynamic_debug/ddebug' file,
+         Dynamic debugging is controlled via the 'dynamic_debug/control' file,

          which is contained in the 'debugfs' filesystem. Thus, the debugfs
          filesystem must first be mounted before making use of this feature.
          which is contained in the 'debugfs' filesystem. Thus, the debugfs
          filesystem must first be mounted before making use of this feature.

-         We refer the control file as: <debugfs>/dynamic_debug/ddebug. This
+         We refer the control file as: <debugfs>/dynamic_debug/control. This

          file contains a list of the debug statements that can be enabled. The
          format for each line of the file is:
 
          file contains a list of the debug statements that can be enabled. The
          format for each line of the file is:
 


@@ -965,7 +1057,7 @@ config DYNAMIC_DEBUG
 
          From a live system:
 
 
          From a live system:
 

-               nullarbor:~ # cat <debugfs>/dynamic_debug/ddebug
+               nullarbor:~ # cat <debugfs>/dynamic_debug/control

                # filename:lineno [module]function flags format
                fs/aio.c:222 [aio]__put_ioctx - "__put_ioctx:\040freeing\040%p\012"
                fs/aio.c:248 [aio]ioctx_alloc - "ENOMEM:\040nr_events\040too\040high\012"
                # filename:lineno [module]function flags format
                fs/aio.c:222 [aio]__put_ioctx - "__put_ioctx:\040freeing\040%p\012"
                fs/aio.c:248 [aio]ioctx_alloc - "ENOMEM:\040nr_events\040too\040high\012"


@@ -975,23 +1067,23 @@ config DYNAMIC_DEBUG
 
                // enable the message at line 1603 of file svcsock.c
                nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
 
                // enable the message at line 1603 of file svcsock.c
                nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >

-                                               <debugfs>/dynamic_debug/ddebug
+                                               <debugfs>/dynamic_debug/control

 
                // enable all the messages in file svcsock.c
                nullarbor:~ # echo -n 'file svcsock.c +p' >
 
                // enable all the messages in file svcsock.c
                nullarbor:~ # echo -n 'file svcsock.c +p' >

-                                               <debugfs>/dynamic_debug/ddebug
+                                               <debugfs>/dynamic_debug/control

 
                // enable all the messages in the NFS server module
                nullarbor:~ # echo -n 'module nfsd +p' >
 
                // enable all the messages in the NFS server module
                nullarbor:~ # echo -n 'module nfsd +p' >

-                                               <debugfs>/dynamic_debug/ddebug
+                                               <debugfs>/dynamic_debug/control

 
                // enable all 12 messages in the function svc_process()
                nullarbor:~ # echo -n 'func svc_process +p' >
 
                // enable all 12 messages in the function svc_process()
                nullarbor:~ # echo -n 'func svc_process +p' >

-                                               <debugfs>/dynamic_debug/ddebug
+                                               <debugfs>/dynamic_debug/control

 
                // disable all 12 messages in the function svc_process()
                nullarbor:~ # echo -n 'func svc_process -p' >
 
                // disable all 12 messages in the function svc_process()
                nullarbor:~ # echo -n 'func svc_process -p' >

-                                               <debugfs>/dynamic_debug/ddebug
+                                               <debugfs>/dynamic_debug/control

 
          See Documentation/dynamic-debug-howto.txt for additional information.
 
 
          See Documentation/dynamic-debug-howto.txt for additional information.
 


@@ -1006,6 +1098,13 @@ config DMA_API_DEBUG
          This option causes a performance degredation.  Use only if you want
          to debug device drivers. If unsure, say N.
 
          This option causes a performance degredation.  Use only if you want
          to debug device drivers. If unsure, say N.
 

+config ATOMIC64_SELFTEST
+       bool "Perform an atomic64_t self-test at boot"
+       help
+         Enable this option to test the atomic64_t functions at boot.
+
+         If unsure, say N.
+

 source "samples/Kconfig"
 
 source "lib/Kconfig.kgdb"
 source "samples/Kconfig"
 
 source "lib/Kconfig.kgdb"