Thread (32 messages) 32 messages, 5 authors, 2017-04-28

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2017-04-28 14:47:43
Also in: linux-arm-kernel, linux-mips, linux-sh, lkml, sparclinux

On Fri, 28 Apr 2017 15:58:10 +0200
Peter Zijlstra [off-list ref] wrote:
On Fri, Apr 28, 2017 at 03:44:23PM +0200, Petr Mladek wrote:
quoted
On Fri 2017-04-28 11:02:26, Peter Zijlstra wrote:  
quoted
On Thu, Apr 27, 2017 at 03:38:19PM +0200, Petr Mladek wrote:  
quoted
Also we need to look for alternatives. There is a chance
to create crashdump and get the ftrace messages from it.
Also this might be scenario when we might need to suggest
the early_printk() patchset from Peter Zijlstra.  
I'd be happy to repost those. I still carry them in my tree.  
You do not need to if they are still the same as
https://lkml.kernel.org/r/20161018170830.405990950@infradead.org  
More or less, I think I fixed an intermediate compile fail reported by
you and the 0-day thing and I wrote a few comments in the last patch.

They live here fwiw:

  git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git debug/tmp
quoted
I rather do not promise anything but I would like to look at them
within next few weeks (after the merge window).  
Sure, I'll post them again during/after the merge window.
BTW, this is what I ended up using to get the debug information I
needed.

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help