lkml.org 
[lkml]   [2016]   [Dec]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] MAINTAINERS: Add printk maintainers
On Thu, Dec 15, 2016 at 12:20:27PM -0500, Steven Rostedt wrote:
> On Thu, 15 Dec 2016 18:12:00 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Thu, Dec 15, 2016 at 03:34:43PM +0100, Petr Mladek wrote:
> > > We have to find the right balance. For example, we do not show
> > > messages immediately in NMI context because there is a risk
> > > of a deadlock.
> >
> > I find the occasional deadlock much preferable to guaranteed no output.
>
> Right, we can't stress the importance of getting output out when it
> happens. A printk dump is the first course of action when debugging a
> crash. And the printk output shows how much progress the computer made.
>
> If all printks are asynchronous, that will be unreliable information.

No, that will be _no_ information, since the 'later' part that does the
flush will never happen.

> And really, that information can be extremely useful, but only if it is
> reliable, otherwise, it becomes useless.

Well, if you want reliable get a UART and those 3 patches I did to force
early_printk :-)


\
 
 \ /
  Last update: 2016-12-15 18:24    [W:0.056 / U:0.812 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site