diff options
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-11-21 20:19:17 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2017-12-11 09:18:29 -0800 |
| commit | a2f2577d96ad060b65eb909dd39b57d676754119 (patch) | |
| tree | f05ed19020bde2f8998d5a8e1ac873bfd7c5d8be /Documentation/locking | |
| parent | 4ced3314fd3a73dabac4e8a41747883eff36c3e8 (diff) | |
| download | linux-stable-a2f2577d96ad060b65eb909dd39b57d676754119.tar.gz linux-stable-a2f2577d96ad060b65eb909dd39b57d676754119.tar.bz2 linux-stable-a2f2577d96ad060b65eb909dd39b57d676754119.zip | |
torture: Eliminate torture_runnable and perf_runnable
The purpose of torture_runnable is to allow rcutorture and locktorture
to be started and stopped via sysfs when they are built into the kernel
(as in not compiled as loadable modules). However, the 0444 permissions
for both instances of torture_runnable prevent this use case from ever
being put into practice. Given that there have been no complaints
about this deficiency, it is reasonable to conclude that no one actually
makes use of this sysfs capability. The perf_runnable module parameter
for rcuperf is in the same situation.
This commit therefore removes both torture_runnable instances as well
as perf_runnable.
Reported-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'Documentation/locking')
| -rw-r--r-- | Documentation/locking/locktorture.txt | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/Documentation/locking/locktorture.txt b/Documentation/locking/locktorture.txt index a2ef3a929bf1..6a8df4cd19bf 100644 --- a/Documentation/locking/locktorture.txt +++ b/Documentation/locking/locktorture.txt @@ -57,11 +57,6 @@ torture_type Type of lock to torture. By default, only spinlocks will o "rwsem_lock": read/write down() and up() semaphore pairs. -torture_runnable Start locktorture at boot time in the case where the - module is built into the kernel, otherwise wait for - torture_runnable to be set via sysfs before starting. - By default it will begin once the module is loaded. - ** Torture-framework (RCU + locking) ** |