summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorAruna Balakrishnaiah <aruna@linux.vnet.ibm.com>2013-06-06 00:21:32 +0530
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2013-06-20 17:04:49 +1000
commitd7563c94f728d8c9228cfddbb044c843b2e243e8 (patch)
treea1aa32537e0a3946f36cc9b5e3f2e05ac2a1c3b2 /fs
parent126746101e89991f179209ef58ab5937bc5ea4a3 (diff)
downloadlinux-d7563c94f728d8c9228cfddbb044c843b2e243e8.tar.gz
linux-d7563c94f728d8c9228cfddbb044c843b2e243e8.tar.xz
powerpc/pseries: Read/Write oops nvram partition via pstore
IBM's p series machines provide persistent storage for LPARs through NVRAM. NVRAM's lnx,oops-log partition is used to log oops messages. Currently the kernel provides the contents of p-series NVRAM only as a simple stream of bytes via /dev/nvram, which must be interpreted in user space by the nvram command in the powerpc-utils package. This patch set exploits the pstore subsystem to expose oops partition in NVRAM as a separate file in /dev/pstore. For instance, Oops messages will be stored in a file named [dmesg-nvram-2]. In case pstore registration fails it will fall back to kmsg_dump mechanism. This patch will read/write the oops messages from/to this partition via pstore. Signed-off-by: Jim Keniston <jkenisto@us.ibm.com> Signed-off-by: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions