From: Paul Mundt <lethal@linux-sh.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: dwmw2@infradead.org, CeLinux <celinux-dev@tree.celinuxforum.org>,
Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: Re: How to store kernel panic/oops
Date: Tue, 29 Dec 2009 16:05:03 +0900 [thread overview]
Message-ID: <20091229070503.GE7638@linux-sh.org> (raw)
In-Reply-To: <4B38F304.4020801@gmail.com>
On Mon, Dec 28, 2009 at 07:03:48PM +0100, Marco Stornelli wrote:
> David Woodhouse wrote:
>
> > Can't it be done with what's in the tree already? Just create an MTD
> > device using phram or something else, then point mtdoops at it
>
> Yes of course, if possible we shouldn't reinvent the wheel but I
> wondered if there was something more specific. To add mtdoops (more or
> less 1k) we have to add mtd subsys (more or less 14k) to the kernel to
> achieve this and it's all overhead.
>
panic/oops information is punted down to a kmsg dumper, which mtdoops
just happens to be one of. If you wanted to do your own platform specific
hack for size constraints you could easily just have your own special
one instead. Take a look at linux/kmsg_dump.h.
prev parent reply other threads:[~2009-12-29 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 18:03 Re: How to store kernel panic/oops Marco Stornelli
2009-12-29 7:05 ` Paul Mundt [this message]
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=20091229070503.GE7638@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=dwmw2@infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
/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).