From: Jim Keniston <jkenisto@us.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: [RFC PATCH 0/6] nvram: Capture oops/panic reports in NVRAM
Date: Sat, 13 Nov 2010 20:15:10 -0800 [thread overview]
Message-ID: <20101114041510.9457.92921.stgit@localhost.localdomain> (raw)
This patch series enables p Series systems to capture oops and panic
reports from the printk buffer into NVRAM, where they can be examined
after reboot using the nvram command.
Patches 1-2 implement the basic feature, and patch 4 adds compression,
so we can capture more of the printk buffer. Patches 3 and 5-6 add
refinements. Patch 5 is not powerpc-specific, and I plan to pursue that
independently on LKML.
This series applies atop the little bug-fix series I posted two days
ago --
"More ppc64 nvram code cleanup"
http://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087009.html
-- which in turn applies atop Ben Herrenschmidt's Aug. 2 patch set --
"[RFC] Clean up ppc64 nvram code"
http://lists.ozlabs.org/pipermail/linuxppc-dev/2010-August/084601.html
My patches have been tested against 2.6.37-rc1.
---
Jim Keniston (6):
Shrink our zlib_deflate workspace from 268K to 24K
Slim down zlib_deflate workspace when possible
Add compression to fit more printk output into NVRAM
Always capture start of oops report to NVRAM
Capture oops/panic reports in ibm,oops-log partition
Generalize code for OS partitions in NVRAM
arch/powerpc/include/asm/nvram.h | 3
arch/powerpc/include/asm/rtas.h | 6
arch/powerpc/kernel/nvram_64.c | 31 ++
arch/powerpc/platforms/pseries/nvram.c | 470 ++++++++++++++++++++++++++++----
include/linux/zlib.h | 14 +
lib/zlib_deflate/deflate.c | 33 ++
lib/zlib_deflate/deflate_syms.c | 1
lib/zlib_deflate/defutil.h | 17 +
8 files changed, 504 insertions(+), 71 deletions(-)
--
Jim Keniston
IBM Linux Technology Center
Beaverton, OR
next reply other threads:[~2010-11-14 4:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 4:15 Jim Keniston [this message]
2010-11-14 4:15 ` [PATCH 1/6] nvram: Generalize code for OS partitions in NVRAM Jim Keniston
2011-02-07 4:57 ` Benjamin Herrenschmidt
2011-02-09 22:43 ` Jim Keniston
2010-11-14 4:15 ` [PATCH 2/6] nvram: Capture oops/panic reports in ibm, oops-log partition Jim Keniston
2011-02-07 5:01 ` Benjamin Herrenschmidt
2011-02-09 23:00 ` Jim Keniston
2010-11-14 4:15 ` [PATCH 3/6] nvram: Always capture start of oops report to NVRAM Jim Keniston
2010-11-14 4:15 ` [PATCH 4/6] nvram: Add compression to fit more printk output into NVRAM Jim Keniston
2010-11-14 4:15 ` [PATCH 5/6] nvram: Slim down zlib_deflate workspace when possible Jim Keniston
2011-02-07 4:39 ` Benjamin Herrenschmidt
2010-11-14 4:15 ` [PATCH 6/6] nvram: Shrink our zlib_deflate workspace from 268K to 24K Jim Keniston
2010-11-14 4:36 ` [RFC PATCH 0/6] nvram: Capture oops/panic reports in NVRAM Jim Keniston
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=20101114041510.9457.92921.stgit@localhost.localdomain \
--to=jkenisto@us.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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 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.