linux/Documentation/trace
Jonathan Corbet 625f2a378e sched: Get rid of lock_depth
Neil Brown pointed out that lock_depth somehow escaped the BKL
removal work.  Let's get rid of it now.

Note that the perf scripting utilities still have a bunch of
code for dealing with common_lock_depth in tracepoints; I have
left that in place in case anybody wants to use that code with
older kernels.

Suggested-by: Neil Brown <neilb@suse.de>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/20110422111910.456c0e84@bike.lwn.net
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2011-04-24 13:18:38 +02:00
..
postprocess
events-kmem.txt
events-power.txt
events.txt
ftrace-design.txt
ftrace.txt tracing: Add an 'overwrite' trace_option. 2011-03-09 13:52:27 -05:00
function-graph-fold.vim
kprobetrace.txt sched: Get rid of lock_depth 2011-04-24 13:18:38 +02:00
mmiotrace.txt
ring-buffer-design.txt Fix common misspellings 2011-03-31 11:26:23 -03:00
tracepoint-analysis.txt
tracepoints.txt