From 39eb7e9791866973dbb7a3a6d2061d70356c7d90 Mon Sep 17 00:00:00 2001 From: Anton Vorontsov Date: Thu, 17 May 2012 00:15:34 -0700 Subject: 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 Acked-by: Marco Stornelli Acked-by: Kees Cook Signed-off-by: Greg Kroah-Hartman --- Documentation/ramoops.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'Documentation/ramoops.txt') 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 = { -- cgit