|
@@ -1373,81 +1373,6 @@ config RCU_TORTURE_TEST
|
|
Say M if you want the RCU torture tests to build as a module.
|
|
Say M if you want the RCU torture tests to build as a module.
|
|
Say N if you are unsure.
|
|
Say N if you are unsure.
|
|
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_PREINIT
|
|
|
|
- bool "Slow down RCU grace-period pre-initialization to expose races"
|
|
|
|
- depends on RCU_TORTURE_TEST
|
|
|
|
- help
|
|
|
|
- This option delays grace-period pre-initialization (the
|
|
|
|
- propagation of CPU-hotplug changes up the rcu_node combining
|
|
|
|
- tree) for a few jiffies between initializing each pair of
|
|
|
|
- consecutive rcu_node structures. This helps to expose races
|
|
|
|
- involving grace-period pre-initialization, in other words, it
|
|
|
|
- makes your kernel less stable. It can also greatly increase
|
|
|
|
- grace-period latency, especially on systems with large numbers
|
|
|
|
- of CPUs. This is useful when torture-testing RCU, but in
|
|
|
|
- almost no other circumstance.
|
|
|
|
-
|
|
|
|
- Say Y here if you want your system to crash and hang more often.
|
|
|
|
- Say N if you want a sane system.
|
|
|
|
-
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_PREINIT_DELAY
|
|
|
|
- int "How much to slow down RCU grace-period pre-initialization"
|
|
|
|
- range 0 5
|
|
|
|
- default 3
|
|
|
|
- depends on RCU_TORTURE_TEST_SLOW_PREINIT
|
|
|
|
- help
|
|
|
|
- This option specifies the number of jiffies to wait between
|
|
|
|
- each rcu_node structure pre-initialization step.
|
|
|
|
-
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_INIT
|
|
|
|
- bool "Slow down RCU grace-period initialization to expose races"
|
|
|
|
- depends on RCU_TORTURE_TEST
|
|
|
|
- help
|
|
|
|
- This option delays grace-period initialization for a few
|
|
|
|
- jiffies between initializing each pair of consecutive
|
|
|
|
- rcu_node structures. This helps to expose races involving
|
|
|
|
- grace-period initialization, in other words, it makes your
|
|
|
|
- kernel less stable. It can also greatly increase grace-period
|
|
|
|
- latency, especially on systems with large numbers of CPUs.
|
|
|
|
- This is useful when torture-testing RCU, but in almost no
|
|
|
|
- other circumstance.
|
|
|
|
-
|
|
|
|
- Say Y here if you want your system to crash and hang more often.
|
|
|
|
- Say N if you want a sane system.
|
|
|
|
-
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_INIT_DELAY
|
|
|
|
- int "How much to slow down RCU grace-period initialization"
|
|
|
|
- range 0 5
|
|
|
|
- default 3
|
|
|
|
- depends on RCU_TORTURE_TEST_SLOW_INIT
|
|
|
|
- help
|
|
|
|
- This option specifies the number of jiffies to wait between
|
|
|
|
- each rcu_node structure initialization.
|
|
|
|
-
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_CLEANUP
|
|
|
|
- bool "Slow down RCU grace-period cleanup to expose races"
|
|
|
|
- depends on RCU_TORTURE_TEST
|
|
|
|
- help
|
|
|
|
- This option delays grace-period cleanup for a few jiffies
|
|
|
|
- between cleaning up each pair of consecutive rcu_node
|
|
|
|
- structures. This helps to expose races involving grace-period
|
|
|
|
- cleanup, in other words, it makes your kernel less stable.
|
|
|
|
- It can also greatly increase grace-period latency, especially
|
|
|
|
- on systems with large numbers of CPUs. This is useful when
|
|
|
|
- torture-testing RCU, but in almost no other circumstance.
|
|
|
|
-
|
|
|
|
- Say Y here if you want your system to crash and hang more often.
|
|
|
|
- Say N if you want a sane system.
|
|
|
|
-
|
|
|
|
-config RCU_TORTURE_TEST_SLOW_CLEANUP_DELAY
|
|
|
|
- int "How much to slow down RCU grace-period cleanup"
|
|
|
|
- range 0 5
|
|
|
|
- default 3
|
|
|
|
- depends on RCU_TORTURE_TEST_SLOW_CLEANUP
|
|
|
|
- help
|
|
|
|
- This option specifies the number of jiffies to wait between
|
|
|
|
- each rcu_node structure cleanup operation.
|
|
|
|
-
|
|
|
|
config RCU_CPU_STALL_TIMEOUT
|
|
config RCU_CPU_STALL_TIMEOUT
|
|
int "RCU CPU stall timeout in seconds"
|
|
int "RCU CPU stall timeout in seconds"
|
|
depends on RCU_STALL_COMMON
|
|
depends on RCU_STALL_COMMON
|