|author||Kees Cook <email@example.com>||2012-05-03 15:45:02 +1000|
|committer||Greg Kroah-Hartman <firstname.lastname@example.org>||2012-05-16 08:06:33 -0700|
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 <email@example.com> Cc: Tony Luck <firstname.lastname@example.org> Cc: Marco Stornelli <email@example.com> Cc: Arnd Bergmann <firstname.lastname@example.org> Cc: Randy Dunlap <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> Signed-off-by: Greg Kroah-Hartman <email@example.com>
Diffstat (limited to 'Documentation/ramoops.txt')
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 8fb1ba7fe7bf..a0b9d8e75380 100644
@@ -3,7 +3,7 @@ Ramoops oops/panic logger
Sergiu Iordache <firstname.lastname@example.org>
-Updated: 8 August 2011
+Updated: 17 November 2011
@@ -71,6 +71,6 @@ timestamp and a new line. The dump then continues with the actual data.
4. Reading the data
-The dump data can be read from memory (through /dev/mem or other means).
-Getting the module parameters, which are needed in order to parse the data, can
-be done through /sys/module/ramoops/parameters/* .
+The dump data can be read from the pstore filesystem. The format for these
+files is "dmesg-ramoops-N", where N is the record number in memory. To delete
+a stored record from RAM, simply unlink the respective pstore file.