tracing: Choose static tp_printk buffer by explicit nesting count
authorAndy Lutomirski <luto@kernel.org>
Thu, 26 May 2016 19:00:33 +0000 (12:00 -0700)
committerSteven Rostedt <rostedt@goodmis.org>
Mon, 20 Jun 2016 13:54:20 +0000 (09:54 -0400)
commite2ace001176dc9745a472fe8bda1f0b28a4d7351
treeb278062869848c20cd6075696ee8271a4b09de62
parent35abb67de744b5dbaec54381f2f9e0246089331d
tracing: Choose static tp_printk buffer by explicit nesting count

Currently, the trace_printk code chooses which static buffer to use based
on what type of atomic context (NMI, IRQ, etc) it's in.  Simplify the
code and make it more robust: simply count the nesting depth and choose
a buffer based on the current nesting depth.

The new code will only drop an event if we nest more than 4 deep,
and the old code was guaranteed to malfunction if that happened.

Link: http://lkml.kernel.org/r/07ab03aecfba25fcce8f9a211b14c9c5e2865c58.1464289095.git.luto@kernel.org
Acked-by: Namhyung Kim <namhyung@kernel.org>
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/trace.c