On Fri, 2012-11-16 at 03:21 +0100, Frederic Weisbecker wrote: > klogd is woken up asynchronously from the tick in order > to do it safely. > > However if printk is called when the tick is stopped, the reader > won't be woken up until the next interrupt, which might not fire > for a while. As a result, the user may miss some message. > > To fix this, lets implement the printk tick using a lazy irq work. > This subsystem takes care of the timer tick state and can > fix up accordingly. > > Signed-off-by: Frederic Weisbecker <[email protected]> > Cc: Peter Zijlstra <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: Andrew Morton <[email protected]> > Cc: Steven Rostedt <[email protected]> > Cc: Paul Gortmaker <[email protected]> > ---
Acked-by: Steven Rostedt <[email protected]> You can add my ack to the rest of this series too. -- Steve -- 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/
