From: Wolfgang Denk <wd@denx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Grant Erickson <gerickson@nuovations.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Add Alternative Log Buffer Support for printk Messages
Date: Sat, 31 Jan 2009 11:01:13 +0100 [thread overview]
Message-ID: <20090131100113.6E1B983644C3@gemini.denx.de> (raw)
In-Reply-To: <20090130142825.e63ee797.akpm@linux-foundation.org>
Dear Andrew,
In message <20090130142825.e63ee797.akpm@linux-foundation.org> you wrote:
>
> It shouldn't be too hard to cook up some way of copying some data into
> th log buffer before the kernel itself has put anything in there, if
> that's all which is needed.
Agreed, but we also want to get the data back into the shared log
buffer when the system crashes someone presses the reset button. The
log buffer shall survive reboots -that's the basic requirment of the
implementation, and this is what makes it a bit more complicated.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Microsoft Multitasking:
several applications can crash at the same time.
next prev parent reply other threads:[~2009-01-31 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 17:39 [RFC] Add Alternative Log Buffer Support for printk Messages Grant Erickson
2009-01-21 20:37 ` David Miller
2009-01-27 13:36 ` Carl-Daniel Hailfinger
2009-01-30 19:51 ` Andrew Morton
2009-01-30 22:01 ` Grant Erickson
2009-01-30 22:28 ` Andrew Morton
2009-01-31 10:01 ` Wolfgang Denk [this message]
2009-01-31 9:59 ` Wolfgang Denk
2009-02-03 1:08 ` Carl-Daniel Hailfinger
2009-02-18 21:27 Timo Juhani Lindfors
[not found] <49D17E5D.30306@gmx.net>
2009-03-31 15:58 ` Grant Erickson
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=20090131100113.6E1B983644C3@gemini.denx.de \
--to=wd@denx.de \
--cc=akpm@linux-foundation.org \
--cc=gerickson@nuovations.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).