Merge tag 'dma-mapping-5.1' of git://git.infradead.org/users/hch/dma-mapping

[linux-2.6-microblaze.git] / lib / Kconfig.debug

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ef5d7c0..bd62be8 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -17,6 +17,23 @@ config PRINTK_TIME
          The behavior is also controlled by the kernel command line
          parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst
 
+config PRINTK_CALLER
+       bool "Show caller information on printks"
+       depends on PRINTK
+       help
+         Selecting this option causes printk() to add a caller "thread id" (if
+         in task context) or a caller "processor id" (if not in task context)
+         to every message.
+
+         This option is intended for environments where multiple threads
+         concurrently call printk() for many times, for it is difficult to
+         interpret without knowing where these lines (or sometimes individual
+         line which was divided into multiple lines due to race) came from.
+
+         Since toggling after boot makes the code racy, currently there is
+         no option to enable/disable at the kernel command line parameter or
+         sysfs interface.
+
 config CONSOLE_LOGLEVEL_DEFAULT
        int "Default console loglevel (1-15)"
        range 1 15
@@ -222,7 +239,6 @@ config ENABLE_MUST_CHECK
 config FRAME_WARN
        int "Warn for stack frames larger than (needs gcc 4.4)"
        range 0 8192
-       default 3072 if KASAN_EXTRA
        default 2048 if GCC_PLUGIN_LATENT_ENTROPY
        default 1280 if (!64BIT && PARISC)
        default 1024 if (!64BIT && !PARISC)
@@ -266,23 +282,6 @@ config UNUSED_SYMBOLS
          you really need it, and what the merge plan to the mainline kernel for
          your module is.
 
-config PAGE_OWNER
-       bool "Track page owner"
-       depends on DEBUG_KERNEL && STACKTRACE_SUPPORT
-       select DEBUG_FS
-       select STACKTRACE
-       select STACKDEPOT
-       select PAGE_EXTENSION
-       help
-         This keeps track of what call chain is the owner of a page, may
-         help to find bare alloc_page(s) leaks. Even if you include this
-         feature on your build, it is disabled in default. You should pass
-         "page_owner=on" to boot parameter in order to enable it. Eats
-         a fair amount of memory if enabled. See tools/vm/page_owner_sort.c
-         for user-space helper.
-
-         If unsure, say N.
-
 config DEBUG_FS
        bool "Debug Filesystem"
        help
@@ -1664,7 +1663,6 @@ if RUNTIME_TESTING_MENU
 config LKDTM
        tristate "Linux Kernel Dump Test Tool Module"
        depends on DEBUG_FS
-       depends on BLOCK
        help
        This module enables testing of the different dumping mechanisms by
        inducing system failures at predefined crash points.
@@ -1840,6 +1838,19 @@ config TEST_LKM
 
          If unsure, say N.
 
+config TEST_VMALLOC
+       tristate "Test module for stress/performance analysis of vmalloc allocator"
+       default n
+       depends on MMU
+       depends on m
+       help
+         This builds the "test_vmalloc" module that should be used for
+         stress and performance analysis. So, any new change for vmalloc
+         subsystem can be evaluated from performance and stability point
+         of view.
+
+         If unsure, say N.
+
 config TEST_USER_COPY
        tristate "Test user/kernel boundary protections"
        depends on m
@@ -1955,6 +1966,28 @@ config TEST_MEMCAT_P
 
          If unsure, say N.
 
+config TEST_LIVEPATCH
+       tristate "Test livepatching"
+       default n
+       depends on DYNAMIC_DEBUG
+       depends on LIVEPATCH
+       depends on m
+       help
+         Test kernel livepatching features for correctness.  The tests will
+         load test modules that will be livepatched in various scenarios.
+
+         To run all the livepatching tests:
+
+         make -C tools/testing/selftests TARGETS=livepatch run_tests
+
+         Alternatively, individual tests may be invoked:
+
+         tools/testing/selftests/livepatch/test-callbacks.sh
+         tools/testing/selftests/livepatch/test-livepatch.sh
+         tools/testing/selftests/livepatch/test-shadow-vars.sh
+
+         If unsure, say N.
+
 config TEST_OBJAGG
        tristate "Perform selftest on object aggreration manager"
        default n
@@ -1963,6 +1996,15 @@ config TEST_OBJAGG
          Enable this option to test object aggregation manager on boot
          (or module load).
 
+
+config TEST_STACKINIT
+       tristate "Test level of stack variable initialization"
+       help
+         Test if the kernel is zero-initializing stack variables and
+         padding. Coverage is controlled by compiler flags,
+         CONFIG_GCC_PLUGIN_STRUCTLEAK, CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF,
+         or CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL.
+
          If unsure, say N.
 
 endif # RUNTIME_TESTING_MENU