On Thu, 5 Jun 2014, Steven Rostedt wrote:
> On Thu, 05 Jun 2014 15:28:32 -0000
> Thomas Gleixner <t...@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 :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
