Messages in this thread | | | Date | Fri, 6 Jun 2014 07:40:41 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: [patch 1/2] rtmutex: Handle deadlock detection smarter |
| |
On Thu, 5 Jun 2014, Steven Rostedt wrote:
> On Thu, 05 Jun 2014 15:28:32 -0000 > Thomas Gleixner <tglx@linutronix.de> wrote: > > > Index: tip/kernel/locking/rtmutex.h > > =================================================================== > > --- tip.orig/kernel/locking/rtmutex.h > > +++ tip/kernel/locking/rtmutex.h > > @@ -21,6 +21,10 @@ > > #define debug_rt_mutex_unlock(l) do { } while (0) > > #define debug_rt_mutex_init(m, n) do { } while (0) > > #define debug_rt_mutex_deadlock(d, a ,l) do { } while (0) > > -#define debug_rt_mutex_print_deadlock(w) do { } while (0) > > #define debug_rt_mutex_detect_deadlock(w,d) (d) > > #define debug_rt_mutex_reset_waiter(w) do { } while (0) > > + > > +static inline void debug_rt_mutex_print_deadlock(struct rt_mutex_waiter *w) > > +{ > > + WARN(1, "rtmutex deadlock detected\n"); > > +} > > > > The above is called directly in rt_mutex_start_proxy_lock(), and as it > doesn't have a conditional where the DEBUG_RT_MUTEXES version does, I > get a ton of these:
Crap, yes. Of course I had debug enabled :)
| |