From: Peter Zijlstra <peterz@infradead.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: torvalds@osdl.org, Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: deadlock caused by printk
Date: Fri, 25 Mar 2011 15:50:27 +0100 [thread overview]
Message-ID: <1301064627.2250.215.camel@laptop> (raw)
In-Reply-To: <AANLkTimw1+6DrYxxzkw7yh-t4W8rM55qcVd1nsQrAYT-@mail.gmail.com>
On Fri, 2011-03-25 at 22:30 +0800, Ming Lei wrote:
>
> But seems ftrace can't dump out the messages if system hangs,
True.
> so could
> we introduce a smart and simple "printk" which can be used in any
> contexts?
I think you could use early_printk() for that, it doesn't bother with
all the syslog muck.
next prev parent reply other threads:[~2011-03-25 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 12:15 deadlock caused by printk Ming Lei
2011-03-25 12:21 ` Peter Zijlstra
2011-03-25 12:26 ` Peter Zijlstra
2011-03-25 14:30 ` Ming Lei
2011-03-25 14:50 ` Peter Zijlstra [this message]
2011-03-25 18:41 ` Steven Rostedt
2011-03-25 18:40 ` 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=1301064627.2250.215.camel@laptop \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tom.leiming@gmail.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox