Prev: [PATCH tip/core/urgent] rcu: Make RCU lockdep check the lockdep_recursion variable
Next: pull request: wireless-2.6 2010-04-15
From: Frederic Weisbecker on 15 Apr 2010 16:20
On Wed, Apr 14, 2010 at 12:20:14PM -0400, Chase Douglas wrote:
> The tracing_off_event() function calls tracing_off() to stop tracing
> when an event occurs. By default, only BUG-type events stop tracing,
> while WARNING type events do not. This is controlled through the
> tracing_off={none,warn,bug} commandline parameter.
>
> Call this function from bug and warning event handlers to enable a user
> to debug their kernel by starting a trace, hitting an event, and then
> retrieving trace info knowing that the trace was stopped right after the
> event was hit.


That's a good idea!


>
> Signed-off-by: Chase Douglas <chase.douglas(a)canonical.com>


Acked-by: Frederic Weisbecker <fweisbec(a)gmail.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH tip/core/urgent] rcu: Make RCU lockdep check the lockdep_recursion variable
Next: pull request: wireless-2.6 2010-04-15