On Tue 2014-11-04 10:52:48, Steven Rostedt wrote: > From: "Steven Rostedt (Red Hat)" <[email protected]> > > Being able to divert printk to call another function besides the normal > logging is useful for such things like NMI handling. If some functions > are to be called from NMI that does printk() it is possible to lock up > the box if the nmi handler triggers when another printk is happening. > > One example of this use is to perform a stack trace on all CPUs via NMI. > But if the NMI is to do the printk() it can cause the system to lock up. > By allowing the printk to be diverted to another function that can safely > record the printk output and then print it when it in a safe context > then NMIs will be safe to call these functions like show_regs(). > > Link: http://lkml.kernel.org/p/[email protected] > > Acked-by: Paul E. McKenney <[email protected]> > Signed-off-by: Steven Rostedt <[email protected]>
Looks fine to me. Reviewed-by: Petr Mladek <[email protected]> Best Regards, Petr -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
