From: Marco Stornelli <marco.stornelli@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yuasa Yoichi <yuasa@linux-mips.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
jamie@shareable.org
Subject: Re: [PATCH v2] char drivers: Ram oops/panic logger
Date: Sat, 13 Mar 2010 09:50:07 +0100 [thread overview]
Message-ID: <4B9B51BF.2070201@gmail.com> (raw)
In-Reply-To: <20100312144854.cb94d9b4.akpm@linux-foundation.org>
Il 12/03/2010 23:48, Andrew Morton ha scritto:
> On Wed, 10 Mar 2010 13:15:25 +0100
> Marco Stornelli <marco.stornelli@gmail.com> wrote:
>
>> 2010/3/10 Yuasa Yoichi <yuasa@linux-mips.org>:
>>> 2010/3/10 Marco Stornelli <marco.stornelli@gmail.com>:
>>>> 2010/3/10 Yuasa Yoichi <yuasa@linux-mips.org>:
>> I meant with the "classic" use of mtdoops, therefore with a flash
>> partition without use MTD_RAM. Using MTD_RAM, it's more or less the
>> same thing, with the exception of "where" you want deploy the log. For
>> example: if in your system you have got a nvram you can use it without
>> problem, you need to specify the address of the nvram to the module.
>> Very simple. I think it's a small driver but very useful, feedback
>> from other embedded guys are welcome.
>
> Seems sensible to me. If you have a machine whose memory is persistent
> across reboots then you reserve an arbitrary 4k hunk of memory for
> collecting oops traces, yes?
Yes.
>
> What tools are used for displaying that memory on the next boot? How
> do those tools distinguish between "valid oops trace" and "garbage
> because it was just powered on"? A magic signature?
For my test I used the program devmem2 to dump the log. In general, you
can read the memory via /dev/mem. There's an header plus a timestamp of
the log. The memory is initialized with blank spaces and the size of the
record is fixed at 4k, so if a program/script doesn't find the header at
next 4k, it means there's garbage and it can stop the read operation.
>
> Should the kernel provide the 4k of memory rather than (or in addition
> to) requiring that the system administrator reserve it and tell the
> kernel about it? That'd be a matter of creating a linker section which
> isn't cleared out by the startup code.
>
>
Yes, it can be an option. My first idea was to write a "general" driver,
with an address in input that it can be related to the reserved RAM as
an NVRAM in the system, however it can be a good idea, why not.
Marco
next prev parent reply other threads:[~2010-03-13 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:41 [PATCH v2] char drivers: Ram oops/panic logger Marco Stornelli
2010-03-10 2:08 ` Yuasa Yoichi
2010-03-10 8:02 ` Marco Stornelli
2010-03-10 9:20 ` Yuasa Yoichi
2010-03-10 12:15 ` Marco Stornelli
2010-03-12 22:48 ` Andrew Morton
2010-03-12 23:31 ` Jamie Lokier
2010-03-13 8:49 ` Marco Stornelli
2010-03-15 3:09 ` Jamie Lokier
2010-03-15 8:11 ` Marco Stornelli
2010-03-13 8:50 ` Marco Stornelli [this message]
2010-03-13 14:50 ` Geert Uytterhoeven
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=4B9B51BF.2070201@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jamie@shareable.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuasa@linux-mips.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).