RE: [RFC][PATCH] kmsg_dumper for NVRAM
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: AmÃrico Wang <xiyou.wangcong@xxxxxxxxx>, Seiji Aguchi <seiji.aguchi@xxxxxxx>
- Subject: RE: [RFC][PATCH] kmsg_dumper for NVRAM
- From: "Luck, Tony" <tony.luck@xxxxxxxxx>
- Date: Tue, 1 Feb 2011 11:46:46 -0800
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: "rdunlap@xxxxxxxxxxxx" <rdunlap@xxxxxxxxxxxx>, "Yu, Fenghua" <fenghua.yu@xxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "hpa@xxxxxxxxx" <hpa@xxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, "tj@xxxxxxxxxx" <tj@xxxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx" <akpm@xxxxxxxxxxxxxxxxxxxx>, "a.p.zijlstra@xxxxxxxxx" <a.p.zijlstra@xxxxxxxxx>, "arnd@xxxxxxxx" <arnd@xxxxxxxx>, "linux-doc@xxxxxxxxxxxxxxx" <linux-doc@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-ia64@xxxxxxxxxxxxxxx" <linux-ia64@xxxxxxxxxxxxxxx>, "dle-develop@xxxxxxxxxxxxxxxxxxxxx" <dle-develop@xxxxxxxxxxxxxxxxxxxxx>, "shiyer@xxxxxxxxxx" <shiyer@xxxxxxxxxx>, "pjones@xxxxxxxxxx" <pjones@xxxxxxxxxx>, Satoru Moriya <satoru.moriya@xxxxxxx>
- In-reply-to: <20110201092942.GD21239@xxxxxxxxxxxxxxxxxx>
- List-id: <linux-ia64.vger.kernel.org>
- References: <5C4C569E8A4B9B42A84A977CF070A35B2C1472ACC8@xxxxxxxxxxxxxxxxxxxxxxx> <20110201092942.GD21239@xxxxxxxxxxxxxxxxxx>
- Thread-index: AcvB8poCc1wclGjEQ1yvoaWvYS7xdQAVLD1A
- Thread-topic: [RFC][PATCH] kmsg_dumper for NVRAM
> This looks like what Tony wanted, pstore.
Yes - this looks like another means to the same end (making console log
Available after a crash).
I wonder whether you could use my pstore file system interface
for this ... you'd need to write a backend that used EFI variable
space to save the pieces of a console log, in much the same way
that I used ERST to stash the pieces.
This might be a bit messy - but I think that it would be
worth doing in order to provide a single user interface
to the kmsg_dump on different architectures, regardless
of the underlying storage method used. I.e. the OS
vendors would just have to write startup scripts to glean
information from /dev/pstore and clear it by removing the
files there. Rather than having one set of scripts that
looks at EFI variables for machines that use that, a different
set for machines that have the sparc64 method of saving in
some special area of ram, and yet another set for a machine
that has some other motherboard magical non volatile storage
that hasn't been designed yet.
-Tony
ÿô.nÇ·®+%˱é¥wÿº{.nÇ·¥{±þ&ºã¶¡Ü}©²ÆzÚj:+v¨þø®w¥þàÞ¨è&¢)ß«a¶Úÿûz¹ÞúÝjÿwèf
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]