drm/amd/display: add dal_asic_id for renoir

[linux.git] / lib / Kconfig.debug

diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 4ac4ca21a30af2b8ed512192d67872bef06d19c6..5960e2980a8a00d536a0d8b1b8f50c5325897ed3 100644 (file)
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -353,23 +353,13 @@ config DEBUG_SECTION_MISMATCH
          which results in the code/data being placed in specific sections.
          The section mismatch analysis is always performed after a full
          kernel build, and enabling this option causes the following
-         additional steps to occur:
+         additional step to occur:
          - Add the option -fno-inline-functions-called-once to gcc commands.
            When inlining a function annotated with __init in a non-init
            function, we would lose the section information and thus
            the analysis would not catch the illegal reference.
            This option tells gcc to inline less (but it does result in
            a larger kernel).
-         - Run the section mismatch analysis for each module/built-in.a file.
-           When we run the section mismatch analysis on vmlinux.o, we
-           lose valuable information about where the mismatch was
-           introduced.
-           Running the analysis for each module/built-in.a file
-           tells where the mismatch happens much closer to the
-           source. The drawback is that the same mismatch is
-           reported at least twice.
-         - Enable verbose reporting from modpost in order to help resolve
-           the section mismatches that are reported.
 
 config SECTION_MISMATCH_WARN_ONLY
        bool "Make section mismatch errors non-fatal"
@@ -1139,7 +1129,7 @@ config PROVE_LOCKING
         the proof of observed correctness is also maintained for an
         arbitrary combination of these separate locking variants.
 
-        For more details, see Documentation/locking/lockdep-design.txt.
+        For more details, see Documentation/locking/lockdep-design.rst.
 
 config LOCK_STAT
        bool "Lock usage statistics"
@@ -1153,7 +1143,7 @@ config LOCK_STAT
        help
         This feature enables tracking lock contention points
 
-        For more details, see Documentation/locking/lockstat.txt
+        For more details, see Documentation/locking/lockstat.rst
 
         This also enables lock events required by "perf lock",
         subcommand of perf.
@@ -2076,6 +2066,14 @@ config TEST_STACKINIT
 
          If unsure, say N.
 
+config TEST_MEMINIT
+       tristate "Test heap/page initialization"
+       help
+         Test if the kernel is zero-initializing heap and page allocations.
+         This can be useful to test init_on_alloc and init_on_free features.
+
+         If unsure, say N.
+
 endif # RUNTIME_TESTING_MENU
 
 config MEMTEST