Re: [PATCH] tracing: Choose static tp_printk buffer by explicit nesting count
From: Steven Rostedt
Date: Tue May 24 2016 - 19:02:28 EST
On Tue, 24 May 2016 15:52:28 -0700
Andy Lutomirski <luto@xxxxxxxxxx> wrote:
> 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.
> Signed-off-by: Andy Lutomirski <luto@xxxxxxxxxx>
A quick scan of this patch looks good. But as the merge window is
currently open, and I'll be traveling next week, I may not get to it
for a couple of weeks.
Can you ping me again sometime after June 7th?
I may just pull this in my next queue and hopefully I remember to
review it ;-)