projects / deliverable / linux.git / blame
| Commit | Line | Data |
|---|---|---|
| ca01d6dd | 1 | config PSTORE |
| 25985edc | 2 | bool "Persistent store support" |
| ca01d6dd | 3 | default n |
| 90ce4ca6 AB |
4 | select ZLIB_DEFLATE |
| 5 | select ZLIB_INFLATE | |
| ca01d6dd TL |
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. | |
| 1894a253 | 16 | |
| f29e5956 AV |
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 | ||
| 060287b8 AV |
24 | config PSTORE_FTRACE |
| 25 | bool "Persistent function tracer" | |
| 26 | depends on PSTORE | |
| 27 | depends on FUNCTION_TRACER | |
| 65f8c95e | 28 | depends on DEBUG_FS |
| 060287b8 AV |
29 | help |
| 30 | With this option kernel traces function calls into a persistent | |
| 31 | ram buffer that can be decoded and dumped after reboot through | |
| 32 | pstore filesystem. It can be used to determine what function | |
| 33 | was last called before a reset or panic. | |
| 34 | ||
| 35 | If unsure, say N. | |
| 36 | ||
| 1894a253 AV |
37 | config PSTORE_RAM |
| 38 | tristate "Log panic/oops to a RAM buffer" | |
| 1894a253 | 39 | depends on PSTORE |
| cddb8751 AV |
40 | depends on HAS_IOMEM |
| 41 | depends on HAVE_MEMBLOCK | |
| 42 | select REED_SOLOMON | |
| 43 | select REED_SOLOMON_ENC8 | |
| 44 | select REED_SOLOMON_DEC8 | |
| 1894a253 AV |
45 | help |
| 46 | This enables panic and oops messages to be logged to a circular | |
| 47 | buffer in RAM where it can be read back at some later point. | |
| 48 | ||
| 49 | Note that for historical reasons, the module will be named | |
| 50 | "ramoops.ko". | |
| 51 | ||
| 52 | For more information, see Documentation/ramoops.txt. |