Re: [PATCH 0/4] [GIT PULL] tracing: recursion and compile fixes

From: Steven Rostedt
Date: Mon Apr 20 2009 - 16:44:58 EST



On Mon, 20 Apr 2009, Frederic Weisbecker wrote:
> > >
> >
> > Hmm, doesn't the trace wakeup test if the runqueue lock is locked or not?
> >
> > -- Steve
> >
>
>
> Hmm, yes it does but that's not the first time we meet this problem
> (sched switch event tracing recursions by the past). So either the
> test doesn't work well or this is about another lock that
> wake_up_common takes...

Ug, it is the task's rq lock. Not the current rq lock. wakeup takes the
runqueue lock of the task. The "runqueue_is_locked" only tests the lock of
current CPU, which is not what we can have.

Thus, the function tracer (gag, and probably the event tracing!) should
not call wakeups.

-- Steve

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/