diff options
| author | Paul E. McKenney <paul.mckenney@linaro.org> | 2011-11-04 20:24:07 (GMT) |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2011-12-11 18:31:47 (GMT) |
| commit | bb3bf7052de520f2d21a1275e95fac7a84d89e4c (patch) | |
| tree | 791d90c55d835ef7f81c6d7fe98efcbbf6872869 /kernel | |
| parent | d5f546d834ddc44539651e9955eb3577b0a3eb8b (diff) | |
| download | linux-bb3bf7052de520f2d21a1275e95fac7a84d89e4c.tar.xz | |
rcu: Control rcutorture startup from kernel boot parameters
Currently, if rcutorture is built into the kernel, it must be manually
started or started from an init script. This is inconvenient for
automated KVM testing, where it is good to be able to fully control
rcutorture execution from the kernel parameters. This patch therefore
adds a module parameter named "rcutorture_runnable" that defaults
to zero ("don't start automatically"), but which can be set to one
to cause rcutorture to start up immediately during boot.
Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'kernel')
| -rw-r--r-- | kernel/rcutorture.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/kernel/rcutorture.c b/kernel/rcutorture.c index ce84091..eed9f46 100644 --- a/kernel/rcutorture.c +++ b/kernel/rcutorture.c @@ -164,6 +164,8 @@ static int stutter_pause_test; #define RCUTORTURE_RUNNABLE_INIT 0 #endif int rcutorture_runnable = RCUTORTURE_RUNNABLE_INIT; +module_param(rcutorture_runnable, int, 0444); +MODULE_PARM_DESC(rcutorture_runnable, "Start rcutorture at boot"); #if defined(CONFIG_RCU_BOOST) && !defined(CONFIG_HOTPLUG_CPU) #define rcu_can_boost() 1 |