[PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Daniel Vetter
Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention is never expected, and the ww deadlock

Re: [PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Steven Rostedt
On Tue, 2013-04-30 at 20:45 +0200, Daniel Vetter wrote: > /** > diff --git a/kernel/mutex.c b/kernel/mutex.c > index 66807c7..1cc3487 100644 > --- a/kernel/mutex.c > +++ b/kernel/mutex.c > @@ -827,6 +827,35 @@ int __sched mutex_trylock(struct mutex *lock) > EXPORT_SYMBOL(mutex_trylock); > >

[PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Daniel Vetter
Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention is never expected, and the ww deadlock

[PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Daniel Vetter
Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention is never expected, and the ww deadlock

Re: [PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Steven Rostedt
On Tue, 2013-04-30 at 20:45 +0200, Daniel Vetter wrote: /** diff --git a/kernel/mutex.c b/kernel/mutex.c index 66807c7..1cc3487 100644 --- a/kernel/mutex.c +++ b/kernel/mutex.c @@ -827,6 +827,35 @@ int __sched mutex_trylock(struct mutex *lock) EXPORT_SYMBOL(mutex_trylock); #ifndef

[PATCH] [RFC] mutex: w/w mutex slowpath debugging

2013-04-30 Thread Daniel Vetter
Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention is never expected, and the ww deadlock