Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable
From: Peter Zijlstra <peterz@infradead.org>
Date: 2015-12-18 12:11:53
Also in:
linux-arm-kernel, linux-mips, linux-sh, lkml, sparclinux
Possibly related (same subject, not in this thread)
- 2015-12-18 · Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable · Petr Mladek <pmladek@suse.com>
- 2015-12-17 · Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable · Andrew Morton <akpm@linux-foundation.org>
- 2015-12-15 · Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable · Petr Mladek <pmladek@suse.com>
- 2015-12-14 · Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable · Daniel Thompson <hidden>
- 2015-12-11 · Re: [PATCH v3 4/4] printk/nmi: Increase the size of NMI buffer and make it configurable · Andrew Morton <akpm@linux-foundation.org>
On Fri, Dec 18, 2015 at 12:29:02PM +0100, Peter Zijlstra wrote:
On Fri, Dec 18, 2015 at 10:18:08AM +0000, Daniel Thompson wrote:quoted
I'm not entirely sure that this is an improvement.What I do these days is delete everything in vprintk_emit() and simply call early_printk().
On that, whoever made the device model use vprintk_emit() broke the debugger (KGDB/KDB) printk intercept, and the whole vprintk_func redirection scheme.