On Mon, 2012-10-29 at 14:28 +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 > before a while. As a result, the user may miss some message.
Just a grammar nit (and goes for your previous patch as well). We say "might not fire for a while." or you could say ".. for some time", but not "before a while" ;-) I wounder what the French translation of that is. -- Steve > > 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]> -- 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/
