Re: [RFC][PATCH] printk: Fixup the nmi printk mess

From: Steven Rostedt
Date: Wed Jun 10 2015 - 11:54:39 EST


On Wed, 10 Jun 2015 17:32:53 +0200
Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> > Note that the backtraces used to be serialized via
> > static arch_spinlock_t lock = __ARCH_SPIN_LOCK_UNLOCKED
> > in the past. See the commit
> > a9edc8809328 ("x86/nmi: Perform a safe NMI stack trace on all CPUs")
>
> We could easily add a static raw_spinlock_t to __printk_nmi_flush() and
> serialize its invocations if people think that is important.

Yes please. One thing about the original change is that it made the NMI
backtraces readable. I hated the interleaving of the backtraces, as it
made it almost impossible to to debug.

-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/