linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: gerickson@nuovations.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Add Alternative Log Buffer Support for printk Messages
Date: Wed, 21 Jan 2009 12:37:39 -0800 (PST)	[thread overview]
Message-ID: <20090121.123739.97186745.davem@davemloft.net> (raw)
In-Reply-To: <1232559586-9164-1-git-send-email-gerickson@nuovations.com>

From: Grant Erickson <gerickson@nuovations.com>
Date: Wed, 21 Jan 2009 09:39:46 -0800

> This merges support for the previously DENX-only kernel feature of
> specifying an alternative, "external" buffer for kernel printk
> messages and their associated metadata. In addition, this ports
> architecture support for this feature from arch/ppc to arch/powerpc.
> 
> When this option is enabled, an architecture- or machine-specific log
> buffer is used for all printk messages. This allows entities such as
> boot loaders (e.g. U-Boot) to place printk-compatible messages into
> this buffer and for the kernel to coalesce them with its normal
> messages.
> 
> Signed-off-by: Grant Erickson <gerickson@nuovations.com>

Nice.

This would also be useful on Sparc where it is possible to tell
the firmware to set aside a piece of physical memory which survives
soft resets and thus can be inspected post reboot.

  reply	other threads:[~2009-01-21 20:37 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 [this message]
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
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=20090121.123739.97186745.davem@davemloft.net \
    --to=davem@davemloft.net \
    --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).