Kconfig.debug 4.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132
  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. select TASKS_RCU
  27. select TASKS_RUDE_RCU
  28. select TASKS_TRACE_RCU
  29. default n
  30. help
  31. This option provides a kernel module that runs performance
  32. tests on the RCU infrastructure. The kernel module may be built
  33. after the fact on the running kernel to be tested, if desired.
  34. Say Y here if you want RCU performance tests to be built into
  35. the kernel.
  36. Say M if you want the RCU performance tests to build as a module.
  37. Say N if you are unsure.
  38. config RCU_TORTURE_TEST
  39. tristate "torture tests for RCU"
  40. depends on DEBUG_KERNEL
  41. select TORTURE_TEST
  42. select SRCU
  43. select TASKS_RCU
  44. select TASKS_RUDE_RCU
  45. select TASKS_TRACE_RCU
  46. default n
  47. help
  48. This option provides a kernel module that runs torture tests
  49. on the RCU infrastructure. The kernel module may be built
  50. after the fact on the running kernel to be tested, if desired.
  51. Say Y here if you want RCU torture tests to be built into
  52. the kernel.
  53. Say M if you want the RCU torture tests to build as a module.
  54. Say N if you are unsure.
  55. config RCU_REF_SCALE_TEST
  56. tristate "Scalability tests for read-side synchronization (RCU and others)"
  57. depends on DEBUG_KERNEL
  58. select TORTURE_TEST
  59. select SRCU
  60. select TASKS_RCU
  61. select TASKS_RUDE_RCU
  62. select TASKS_TRACE_RCU
  63. default n
  64. help
  65. This option provides a kernel module that runs performance tests
  66. useful comparing RCU with various read-side synchronization mechanisms.
  67. The kernel module may be built after the fact on the running kernel to be
  68. tested, if desired.
  69. Say Y here if you want these performance tests built into the kernel.
  70. Say M if you want to build it as a module instead.
  71. Say N if you are unsure.
  72. config RCU_CPU_STALL_TIMEOUT
  73. int "RCU CPU stall timeout in seconds"
  74. depends on RCU_STALL_COMMON
  75. range 3 300
  76. default 21
  77. help
  78. If a given RCU grace period extends more than the specified
  79. number of seconds, a CPU stall warning is printed. If the
  80. RCU grace period persists, additional CPU stall warnings are
  81. printed at more widely spaced intervals.
  82. config RCU_TRACE
  83. bool "Enable tracing for RCU"
  84. depends on DEBUG_KERNEL
  85. default y if TREE_RCU
  86. select TRACE_CLOCK
  87. help
  88. This option enables additional tracepoints for ftrace-style
  89. event tracing.
  90. Say Y here if you want to enable RCU tracing
  91. Say N if you are unsure.
  92. config RCU_EQS_DEBUG
  93. bool "Provide debugging asserts for adding NO_HZ support to an arch"
  94. depends on DEBUG_KERNEL
  95. help
  96. This option provides consistency checks in RCU's handling of
  97. NO_HZ. These checks have proven quite helpful in detecting
  98. bugs in arch-specific NO_HZ code.
  99. Say N here if you need ultimate kernel/user switch latencies
  100. Say Y if you are unsure
  101. config RCU_STRICT_GRACE_PERIOD
  102. bool "Provide debug RCU implementation with short grace periods"
  103. depends on DEBUG_KERNEL && RCU_EXPERT
  104. default n
  105. select PREEMPT_COUNT if PREEMPT=n
  106. help
  107. Select this option to build an RCU variant that is strict about
  108. grace periods, making them as short as it can. This limits
  109. scalability, destroys real-time response, degrades battery
  110. lifetime and kills performance. Don't try this on large
  111. machines, as in systems with more than about 10 or 20 CPUs.
  112. But in conjunction with tools like KASAN, it can be helpful
  113. when looking for certain types of RCU usage bugs, for example,
  114. too-short RCU read-side critical sections.
  115. endmenu # "RCU Debugging"