Kconfig.debug 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136
  1. # SPDX-License-Identifier: GPL-2.0-only
  2. #
  3. # RCU-related debugging configuration options
  4. #
  5. menu "RCU Debugging"
  6. config PROVE_RCU
  7. def_bool PROVE_LOCKING
  8. config PROVE_RCU_LIST
  9. bool "RCU list lockdep debugging"
  10. depends on PROVE_RCU && RCU_EXPERT
  11. default n
  12. help
  13. Enable RCU lockdep checking for list usages. By default it is
  14. turned off since there are several list RCU users that still
  15. need to be converted to pass a lockdep expression. To prevent
  16. false-positive splats, we keep it default disabled but once all
  17. users are converted, we can remove this config option.
  18. config TORTURE_TEST
  19. tristate
  20. default n
  21. config RCU_SCALE_TEST
  22. tristate "performance tests for RCU"
  23. depends on DEBUG_KERNEL
  24. select TORTURE_TEST
  25. select SRCU
  26. default n
  27. help
  28. This option provides a kernel module that runs performance
  29. tests on the RCU infrastructure. The kernel module may be built
  30. after the fact on the running kernel to be tested, if desired.
  31. Say Y here if you want RCU performance tests to be built into
  32. the kernel.
  33. Say M if you want the RCU performance tests to build as a module.
  34. Say N if you are unsure.
  35. config RCU_TORTURE_TEST
  36. tristate "torture tests for RCU"
  37. depends on DEBUG_KERNEL
  38. select TORTURE_TEST
  39. select SRCU
  40. default n
  41. help
  42. This option provides a kernel module that runs torture tests
  43. on the RCU infrastructure. The kernel module may be built
  44. after the fact on the running kernel to be tested, if desired.
  45. Say Y here if you want RCU torture tests to be built into
  46. the kernel.
  47. Say M if you want the RCU torture tests to build as a module.
  48. Say N if you are unsure.
  49. config RCU_REF_SCALE_TEST
  50. tristate "Scalability tests for read-side synchronization (RCU and others)"
  51. depends on DEBUG_KERNEL
  52. select TORTURE_TEST
  53. select SRCU
  54. default n
  55. help
  56. This option provides a kernel module that runs performance tests
  57. useful comparing RCU with various read-side synchronization mechanisms.
  58. The kernel module may be built after the fact on the running kernel to be
  59. tested, if desired.
  60. Say Y here if you want these performance tests built into the kernel.
  61. Say M if you want to build it as a module instead.
  62. Say N if you are unsure.
  63. config RCU_CPU_STALL_TIMEOUT
  64. int "RCU CPU stall timeout in seconds"
  65. depends on RCU_STALL_COMMON
  66. range 3 300
  67. default 21
  68. help
  69. If a given RCU grace period extends more than the specified
  70. number of seconds, a CPU stall warning is printed. If the
  71. RCU grace period persists, additional CPU stall warnings are
  72. printed at more widely spaced intervals.
  73. config RCU_EXP_CPU_STALL_TIMEOUT
  74. int "Expedited RCU CPU stall timeout in milliseconds"
  75. depends on RCU_STALL_COMMON
  76. range 0 21000
  77. default 0
  78. help
  79. If a given expedited RCU grace period extends more than the
  80. specified number of milliseconds, a CPU stall warning is printed.
  81. If the RCU grace period persists, additional CPU stall warnings
  82. are printed at more widely spaced intervals. A value of zero
  83. says to use the RCU_CPU_STALL_TIMEOUT value converted from
  84. seconds to milliseconds.
  85. config RCU_TRACE
  86. bool "Enable tracing for RCU"
  87. depends on DEBUG_KERNEL
  88. default y if TREE_RCU
  89. select TRACE_CLOCK
  90. help
  91. This option enables additional tracepoints for ftrace-style
  92. event tracing.
  93. Say Y here if you want to enable RCU tracing
  94. Say N if you are unsure.
  95. config RCU_EQS_DEBUG
  96. bool "Provide debugging asserts for adding NO_HZ support to an arch"
  97. depends on DEBUG_KERNEL
  98. help
  99. This option provides consistency checks in RCU's handling of
  100. NO_HZ. These checks have proven quite helpful in detecting
  101. bugs in arch-specific NO_HZ code.
  102. Say N here if you need ultimate kernel/user switch latencies
  103. Say Y if you are unsure
  104. config RCU_STRICT_GRACE_PERIOD
  105. bool "Provide debug RCU implementation with short grace periods"
  106. depends on DEBUG_KERNEL && RCU_EXPERT && NR_CPUS <= 4 && !TINY_RCU
  107. default n
  108. select PREEMPT_COUNT if PREEMPT=n
  109. help
  110. Select this option to build an RCU variant that is strict about
  111. grace periods, making them as short as it can. This limits
  112. scalability, destroys real-time response, degrades battery
  113. lifetime and kills performance. Don't try this on large
  114. machines, as in systems with more than about 10 or 20 CPUs.
  115. But in conjunction with tools like KASAN, it can be helpful
  116. when looking for certain types of RCU usage bugs, for example,
  117. too-short RCU read-side critical sections.
  118. endmenu # "RCU Debugging"