aboutsummaryrefslogtreecommitdiff
path: root/drivers/char/Kconfig
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2012-05-03 15:45:02 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-05-16 08:06:33 -0700
commit9ba80d99c86f1b76df891afdf39b44df38bbd35b (patch)
treef011fd0ac2adb5cf2a36b15cce0d0b135acaaf09 /drivers/char/Kconfig
parent7dd8e9be9dba1dc5f0dfec67e37076b9c56a97d7 (diff)
downloadlinux-9ba80d99c86f1b76df891afdf39b44df38bbd35b.tar.gz
ramoops: use pstore interface
Instead of using /dev/mem directly and forcing userspace to know (or extract) where the platform has defined persistent memory, how many slots it has, the sizes, etc, use the common pstore infrastructure to handle Oops gathering and extraction. This presents a much easier to use filesystem-based view to the memory region. This also means that any other tools that are written to understand pstore will automatically be able to process ramoops too. Signed-off-by: Kees Cook <keescook@chromium.org> Cc: Tony Luck <tony.luck@intel.com> Cc: Marco Stornelli <marco.stornelli@gmail.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/char/Kconfig')
-rw-r--r--drivers/char/Kconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
index ee946865d6c..fab778d471c 100644
--- a/drivers/char/Kconfig
+++ b/drivers/char/Kconfig
@@ -588,6 +588,7 @@ source "drivers/s390/char/Kconfig"
config RAMOOPS
tristate "Log panic/oops to a RAM buffer"
depends on HAS_IOMEM
+ depends on PSTORE
default n
help
This enables panic and oops messages to be logged to a circular