From: Mike Frysinger <vapier.adi@gmail.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: to@dvomlehn-lnx2.corp.sa.net,
"linux-embedded@vger.kernel.org"@cisco.com,
linux-embedded@vger.kernel.org, akpm@linux-foundation.org,
dwm2@infradead.org, mpm@selenic.com,
paul.gortmaker@windriver.com
Subject: Re: [PATCH] Pseudo-console for capture and redirection of console output
Date: Mon, 12 Apr 2010 02:40:37 -0400 [thread overview]
Message-ID: <p2g8bd0f97a1004112340u547f244bpe0e4f1c9880f0c35@mail.gmail.com> (raw)
In-Reply-To: <20100412063545.GA28646@dvomlehn-lnx2.corp.sa.net>
On Mon, Apr 12, 2010 at 02:35, David VomLehn wrote:
> Provide functions for capturing console output for storage. The primary user
> is likely to be embedded systems that don't have the storage for core dumps
> but do have a need to log kernel panic information for later evaluation. It
> offers two main areas of functionality:
>
> o It can maintain a circular log of console output so that kernel log
> messages written before panic() was called can be retrieved to be
> added to the failure log.
> o A function can be registered to store output from printk() in a
> persistent location, such as a reserved location in RAM. Then,
> printk() can be used either directly, to print state information, or
> indirectly, through standard functions like dump_stack() and
> show_regs().
how is this any different from the already existing mtdoops driver ?
-mike
next prev parent reply other threads:[~2010-04-12 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 6:35 [PATCH] Pseudo-console for capture and redirection of console output David VomLehn
2010-04-12 6:40 ` Mike Frysinger [this message]
2010-04-14 20:30 ` David VomLehn
2010-04-12 7:06 ` Marco Stornelli
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=p2g8bd0f97a1004112340u547f244bpe0e4f1c9880f0c35@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc="linux-embedded@vger.kernel.org"@cisco.com \
--cc=akpm@linux-foundation.org \
--cc=dvomlehn@cisco.com \
--cc=dwm2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=paul.gortmaker@windriver.com \
--cc=to@dvomlehn-lnx2.corp.sa.net \
/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.