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
..
2015-09-08 11:46:48 -07:00
2015-09-01 12:18:40 -07:00
2015-09-09 10:55:32 -07:00
2015-08-28 22:59:36 -04:00
2015-09-03 10:01:44 -07:00
2015-09-08 16:26:18 -07:00
2015-06-08 16:43:09 -06:00
2014-12-10 17:41:10 -08:00
2015-06-26 14:51:15 -07:00
2015-06-08 23:15:45 +02:00
2015-06-26 11:23:38 -04:00
2015-09-02 12:22:54 -07:00
2015-07-14 12:35:42 -06:00
2015-08-22 14:57:59 -07:00
2015-09-10 13:29:01 -07:00
2015-06-24 20:01:36 -07:00
2015-02-27 11:44:24 -08:00
2015-06-24 18:17:40 +02:00
2014-12-08 09:07:11 -05:00
2015-06-23 06:49:44 -06:00
2014-09-23 23:44:16 -07:00