path: root/Documentation/ramoops.txt
diff options
authorAnton Vorontsov <anton.vorontsov@linaro.org>2012-05-17 00:15:34 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-05-17 08:51:59 -0700
commit39eb7e9791866973dbb7a3a6d2061d70356c7d90 (patch)
treebfd4e74f43031fa0ae05636c215a3a60a7f5ae23 /Documentation/ramoops.txt
parent896fc1f0c4c6c19b270734f274be67cb0e8a24af (diff)
pstore/ram: Add ECC support
This is now straightforward: just introduce a module parameter and pass the needed value to persistent_ram_new(). Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org> Acked-by: Marco Stornelli <marco.stornelli@gmail.com> Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/ramoops.txt')
1 files changed, 6 insertions, 0 deletions
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 470d2c4db6ff..4ba7db231cb2 100644
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramoops.txt
@@ -30,6 +30,11 @@ variable while setting 0 in that variable dumps only the panics.
The module uses a counter to record multiple dumps but the counter gets reset
on restart (i.e. new dumps after the restart will overwrite old ones).
+Ramoops also supports software ECC protection of persistent memory regions.
+This might be useful when a hardware reset was used to bring the machine back
+to life (i.e. a watchdog triggered). In such cases, RAM may be somewhat
+corrupt, but usually it is restorable.
2. Setting the parameters
Setting the ramoops parameters can be done in 2 different manners:
@@ -46,6 +51,7 @@ static struct ramoops_platform_data ramoops_data = {
.mem_address = <...>,
.record_size = <...>,
.dump_oops = <...>,
+ .ecc = <...>,
static struct platform_device ramoops_dev = {

Privacy Policy