aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/rcutorture/configs
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2017-04-14 16:12:52 -0700
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2017-06-08 08:25:24 -0700
commit9683937df9ebf4eb62cdedb09c5f20a0760c7d80 (patch)
treec54cae4bb6d5434178cf962d6c31c45827a60e0c /tools/testing/selftests/rcutorture/configs
parentrcu: Complain if blocking in preemptible RCU read-side critical section (diff)
downloadlinux-dev-9683937df9ebf4eb62cdedb09c5f20a0760c7d80.tar.xz
linux-dev-9683937df9ebf4eb62cdedb09c5f20a0760c7d80.zip
rcuperf: Defer expedited/normal check to end of test
Current rcuperf startup checks to see if the user asked to measure only expedited grace periods, yet constrained all grace periods to be normal, or if the user asked to measure only normal grace periods, yet constrained all grace periods to be expedited. Useless tests of this sort are aborted. Unfortunately, making RCU work through the mid-boot dead zone [1] puts RCU into expedited-only mode during that zone. Which happens to also be the exact time that rcuperf carries out the aforementioned check. So if the user asks rcuperf to measure only normal grace periods (the default), rcuperf will now always complain and terminate the test. This commit therefore moves the checks to rcu_perf_cleanup(). This has the disadvantage of failing to abort useless tests, but avoids the need to create yet another kthread and the need to do fiddly checks involving the holdoff time. (Yes, another approach is to do the checks in a late-stage init function, but that would require some way to communicate badness to rcuperf's kthreads, and seems not worth the bother.) [1] https://lwn.net/Articles/716148/ Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/testing/selftests/rcutorture/configs')
0 files changed, 0 insertions, 0 deletions