diff options
| author | Paul E. McKenney <paulmck@kernel.org> | 2019-08-15 20:43:53 +0200 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2019-10-05 20:50:18 +0200 |
| commit | fbbd5e358cecb5fa490550ace66463517a7577e8 (patch) | |
| tree | c251b136d8d2b2f28b351d6bbbd3d31c97f2ce06 /kernel/rcu | |
| parent | rcutorture: Separate warnings for each failure type (diff) | |
| download | linux-fbbd5e358cecb5fa490550ace66463517a7577e8.tar.xz linux-fbbd5e358cecb5fa490550ace66463517a7577e8.zip | |
rcutorture: Make in-kernel-loop testing more brutal
The rcu_torture_fwd_prog_nr() tests the ability of RCU to tolerate
in-kernel busy loops. It invokes rcu_torture_fwd_prog_cond_resched()
within its delay loop, which, in PREEMPT && NO_HZ_FULL kernels results
in the occasional direct call to schedule(). Now, this direct call to
schedule() is appropriate for call_rcu() flood testing, in which either
the kernel should restrain itself or userspace transitions will supply
the needed restraint. But in pure in-kernel loops, the occasional
cond_resched() should do the job.
This commit therefore makes rcu_torture_fwd_prog_nr() use cond_resched()
instead of rcu_torture_fwd_prog_cond_resched() in order to increase the
brutality of this aspect of rcutorture testing.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'kernel/rcu')
| -rw-r--r-- | kernel/rcu/rcutorture.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/kernel/rcu/rcutorture.c b/kernel/rcu/rcutorture.c index 5ac467293803..df1caa93ee63 100644 --- a/kernel/rcu/rcutorture.c +++ b/kernel/rcu/rcutorture.c @@ -1806,7 +1806,7 @@ static void rcu_torture_fwd_prog_nr(int *tested, int *tested_tries) udelay(10); cur_ops->readunlock(idx); if (!fwd_progress_need_resched || need_resched()) - rcu_torture_fwd_prog_cond_resched(1); + cond_resched(); } (*tested_tries)++; if (!time_before(jiffies, stopat) && |