| 1 | config PSTORE |
| 2 | bool "Persistent store support" |
| 3 | default n |
| 4 | select ZLIB_DEFLATE |
| 5 | select ZLIB_INFLATE |
| 6 | help |
| 7 | This option enables generic access to platform level |
| 8 | persistent storage via "pstore" filesystem that can |
| 9 | be mounted as /dev/pstore. Only useful if you have |
| 10 | a platform level driver that registers with pstore to |
| 11 | provide the data, so you probably should just go say "Y" |
| 12 | (or "M") to a platform specific persistent store driver |
| 13 | (e.g. ACPI_APEI on X86) which will select this for you. |
| 14 | If you don't have a platform persistent store driver, |
| 15 | say N. |
| 16 | |
| 17 | config PSTORE_CONSOLE |
| 18 | bool "Log kernel console messages" |
| 19 | depends on PSTORE |
| 20 | help |
| 21 | When the option is enabled, pstore will log all kernel |
| 22 | messages, even if no oops or panic happened. |
| 23 | |
| 24 | config PSTORE_PMSG |
| 25 | bool "Log user space messages" |
| 26 | depends on PSTORE |
| 27 | help |
| 28 | When the option is enabled, pstore will export a character |
| 29 | interface /dev/pmsg0 to log user space messages. On reboot |
| 30 | data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID]. |
| 31 | |
| 32 | If unsure, say N. |
| 33 | |
| 34 | config PSTORE_FTRACE |
| 35 | bool "Persistent function tracer" |
| 36 | depends on PSTORE |
| 37 | depends on FUNCTION_TRACER |
| 38 | depends on DEBUG_FS |
| 39 | help |
| 40 | With this option kernel traces function calls into a persistent |
| 41 | ram buffer that can be decoded and dumped after reboot through |
| 42 | pstore filesystem. It can be used to determine what function |
| 43 | was last called before a reset or panic. |
| 44 | |
| 45 | If unsure, say N. |
| 46 | |
| 47 | config PSTORE_RAM |
| 48 | tristate "Log panic/oops to a RAM buffer" |
| 49 | depends on PSTORE |
| 50 | depends on HAS_IOMEM |
| 51 | depends on HAVE_MEMBLOCK |
| 52 | select REED_SOLOMON |
| 53 | select REED_SOLOMON_ENC8 |
| 54 | select REED_SOLOMON_DEC8 |
| 55 | help |
| 56 | This enables panic and oops messages to be logged to a circular |
| 57 | buffer in RAM where it can be read back at some later point. |
| 58 | |
| 59 | Note that for historical reasons, the module will be named |
| 60 | "ramoops.ko". |
| 61 | |
| 62 | For more information, see Documentation/ramoops.txt. |