From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add printk maintainers
Date: Thu, 15 Dec 2016 18:23:36 +0100 [thread overview]
Message-ID: <20161215172336.GA3124@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20161215122027.0f18bfb1@gandalf.local.home>
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 :-)
next prev parent reply other threads:[~2016-12-15 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 10:47 [PATCH] MAINTAINERS: Add printk maintainers Petr Mladek
2016-12-15 13:48 ` Steven Rostedt
2016-12-15 14:34 ` Petr Mladek
2016-12-15 17:12 ` Peter Zijlstra
2016-12-15 17:20 ` Steven Rostedt
2016-12-15 17:23 ` Peter Zijlstra [this message]
2016-12-15 17:36 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161215172336.GA3124@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.