linux/tools/testing/selftests/rcutorture
Davidlohr Bueso 095777c417 locktorture: Support rtmutex torturing
Real time mutexes is one of the few general primitives
that we do not have in locktorture. Address this -- a few
considerations:

o To spice things up, enable competing thread(s) to become
rt, such that we can stress different prio boosting paths
in the rtmutex code. Introduce a ->task_boost callback,
only used by rtmutex-torturer. Tasks will boost/deboost
around every 50k (arbitrarily) lock/unlock operations.

o Hold times are similar to what we have for other locks:
only occasionally having longer hold times (per ~200k ops).
So we roughly do two full rt boost+deboosting ops with
short hold times.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
2015-10-06 11:24:40 -07:00
..
bin rcutorture: Allow repetition factors in Kconfig-fragment lists 2015-05-27 13:00:00 -07:00
configs locktorture: Support rtmutex torturing 2015-10-06 11:24:40 -07:00
doc rcu: Remove CONFIG_RCU_CPU_STALL_INFO 2015-07-17 14:58:44 -07:00
.gitignore rcutorture: Add KVM-based test framework 2013-12-03 10:11:10 -08:00