mm/cma_debug.c: remove static scoped cma_debugfs_root

[linux.git] / lib / Kconfig.debug

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 1af29b8224fdff289c210af95d3d9228769dbd2e..e6a7b01932e6cd82934242bd2ad287a11d2f683d 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -222,7 +222,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 +265,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
@@ -439,7 +421,7 @@ config DEBUG_KERNEL
 
 menu "Memory Debugging"
 
-source mm/Kconfig.debug
+source "mm/Kconfig.debug"
 
 config DEBUG_OBJECTS
        bool "Debug object operations"
@@ -593,6 +575,21 @@ config DEBUG_KMEMLEAK_DEFAULT_OFF
          Say Y here to disable kmemleak by default. It can then be enabled
          on the command line via kmemleak=on.
 
+config DEBUG_KMEMLEAK_AUTO_SCAN
+       bool "Enable kmemleak auto scan thread on boot up"
+       default y
+       depends on DEBUG_KMEMLEAK
+       help
+         Depending on the cpu, kmemleak scan may be cpu intensive and can
+         stall user tasks at times. This option enables/disables automatic
+         kmemleak scan at boot up.
+
+         Say N here to disable kmemleak auto scan thread to stop automatic
+         scanning. Disabling this option disables automatic reporting of
+         memory leaks.
+
+         If unsure, say Y.
+
 config DEBUG_STACK_USAGE
        bool "Stack utilization instrumentation"
        depends on DEBUG_KERNEL && !IA64
@@ -1609,7 +1606,7 @@ config LATENCYTOP
          Enable this option if you want to use the LatencyTOP tool
          to find out which userspace is blocking on what kernel operations.
 
-source kernel/trace/Kconfig
+source "kernel/trace/Kconfig"
 
 config PROVIDE_OHCI1394_DMA_INIT
        bool "Remote debugging over FireWire early on boot"
@@ -1861,6 +1858,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
@@ -1976,6 +1986,16 @@ config TEST_MEMCAT_P
 
          If unsure, say N.
 
+config TEST_OBJAGG
+       tristate "Perform selftest on object aggreration manager"
+       default n
+       depends on OBJAGG
+       help
+         Enable this option to test object aggregation manager on boot
+         (or module load).
+
+         If unsure, say N.
+
 endif # RUNTIME_TESTING_MENU
 
 config MEMTEST