From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
"David S. Miller" <davem@davemloft.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Fabio M. Di Nitto" <fdinitto@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Olaf Hering <olaf@aepfle.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Tejun Heo <tj@kernel.org>, "H. Peter Anvin" <hpa@linux.intel.com>,
Yinghai LU <yinghai@kernel.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/5] Persist printk buffer across reboots.
Date: Tue, 13 Mar 2012 15:10:49 -0700 [thread overview]
Message-ID: <20120313151049.fa33d232.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120313170851.GA5218@fifo99.com>
On Tue, 13 Mar 2012 10:08:51 -0700
Daniel Walker <dwalker@fifo99.com> wrote:
> On Tue, Mar 13, 2012 at 01:36:36AM -0400, Avery Pennarun wrote:
> > The last patch in this series implements a new CONFIG_PRINTK_PERSIST option
> > that, when enabled, puts the printk buffer in a well-defined memory location
> > so that we can keep appending to it after a reboot. The upshot is that,
> > even after a kernel panic or non-panic hard lockup, on the next boot
> > userspace will be able to grab the kernel messages leading up to it. It
> > could then upload the messages to a server (for example) to keep crash
> > statistics.
>
> There's currently driver/mtd/mtdoops.c, fs/pstore/, and
> drivers/staging/android/ram_console.c that do similar things
> as this. Did you investigate those for potentially modifying them to add
> this functionality ? If so what issues did you find?
>
> I have a arm MSM G1 with persistent memory at 0x16d00000 size 20000bytes..
> It's fairly simple you just have to ioremap the memory, but then it's good
> for writing.. Currently the android ram_console uses this. How would I
> convert this area for use with your changes?
Yes, and various local implementations which do things such as stuffing
the log buffer into NVRAM as the kernel is crashing.
I do think we'd need some back-end driver arrangement which will permit
the use of stores which aren't in addressible mamory.
It's quite the can of worms, but definitely worth doing if we can get
it approximately correct.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-03-13 22:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:36 [PATCH 0/5] Persist printk buffer across reboots Avery Pennarun
2012-03-13 5:36 ` [PATCH 1/5] mm: bootmem: BUG() if you try to allocate bootmem too late Avery Pennarun
2012-03-13 5:36 ` [PATCH 2/5] mm: bootmem: it's okay to reserve_bootmem an invalid address Avery Pennarun
2012-03-13 5:36 ` [PATCH 3/5] mm: nobootmem: implement reserve_bootmem() in terms of memblock Avery Pennarun
2012-03-13 5:36 ` [PATCH 4/5] printk: use alloc_bootmem() instead of memblock_alloc() Avery Pennarun
2012-03-13 6:13 ` Yinghai Lu
2012-03-13 6:40 ` Avery Pennarun
2012-03-13 8:26 ` Ingo Molnar
2012-03-13 21:50 ` Yinghai Lu
2012-03-14 2:23 ` Avery Pennarun
2012-03-13 5:36 ` [PATCH 5/5] printk: CONFIG_PRINTK_PERSIST: persist printk buffer across reboots Avery Pennarun
2012-03-13 5:53 ` [PATCH 0/5] Persist " David Miller
2012-03-13 6:00 ` Avery Pennarun
2012-03-13 6:50 ` David Miller
2012-03-13 7:14 ` Avery Pennarun
2012-03-13 7:18 ` David Miller
2012-03-13 8:10 ` Avery Pennarun
2012-03-13 8:16 ` David Miller
2012-03-13 13:50 ` Peter Zijlstra
2012-03-14 1:57 ` Daniel Walker
2012-03-13 8:32 ` Stephen Boyd
2012-03-13 17:08 ` Daniel Walker
2012-03-13 22:10 ` Andrew Morton [this message]
2012-03-14 2:19 ` Daniel Walker
2012-03-15 22:10 ` Seiji Aguchi
2012-03-14 2:21 ` Avery Pennarun
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=20120313151049.fa33d232.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=apenwarr@gmail.com \
--cc=davem@davemloft.net \
--cc=dwalker@fifo99.com \
--cc=fdinitto@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hpa@linux.intel.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=olaf@aepfle.de \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tj@kernel.org \
--cc=yinghai@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).