locktorture: Teach about lock debugging

Browse source

Regular locks are very different than locks with debugging. For instance
for mutexes, debugging forces to only take the slowpaths. As such, the
locktorture module should take this into account when printing related
information -- specifically when printing user passed parameters, it seems
the right place for such info.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

...

This commit is contained in:

Davidlohr Bueso 2014-09-11 20:40:19 -07:00 • committed by Paul E. McKenney

parent 42ddc75ddd

commit f095bfc0ea

1 changed files with 13 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

15

kernel/locking/locktorture.c

View file