Re: [PATCH tip/core/rcu 03/28] locktorture: Track time of last ->writeunlock()

2020-11-06 Thread Paul E. McKenney
On Thu, Nov 05, 2020 at 10:56:42PM -0800, Davidlohr Bueso wrote: > On Thu, 05 Nov 2020, paul...@kernel.org wrote: > > > From: "Paul E. McKenney" > > > > This commit adds a last_lock_release variable that tracks the time of > > the last ->writeunlock() call, which allows easier diagnosing of

Re: [PATCH tip/core/rcu 03/28] locktorture: Track time of last ->writeunlock()

2020-11-05 Thread Davidlohr Bueso
On Thu, 05 Nov 2020, paul...@kernel.org wrote: From: "Paul E. McKenney" This commit adds a last_lock_release variable that tracks the time of the last ->writeunlock() call, which allows easier diagnosing of lock hangs when using a kernel debugger. This makes sense to have. Acked-by:

[PATCH tip/core/rcu 03/28] locktorture: Track time of last ->writeunlock()

2020-11-05 Thread paulmck
From: "Paul E. McKenney" This commit adds a last_lock_release variable that tracks the time of the last ->writeunlock() call, which allows easier diagnosing of lock hangs when using a kernel debugger. Cc: Davidlohr Bueso Signed-off-by: Paul E. McKenney --- kernel/locking/locktorture.c | 2 ++