locktorture: Teach about lock debugging
authorDavidlohr Bueso <dave@stgolabs.net>
Fri, 12 Sep 2014 03:40:19 +0000 (20:40 -0700)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Tue, 16 Sep 2014 20:41:04 +0000 (13:41 -0700)
commitf095bfc0ea04829d6962edaf06a5c56e0c251f5b
tree6608b20410d7ec3a6474c8ab56992bf037912dcb
parent42ddc75ddd478edac6ad9dc8c63abb4441541af2
locktorture: Teach about lock debugging

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>
kernel/locking/locktorture.c