2 tristate "Persistent store support"
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,
18 bool "Log kernel console messages"
21 When the option is enabled, pstore will log all kernel
22 messages, even if no oops or panic happened.
25 bool "Log user space messages"
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].
35 bool "Persistent function tracer"
37 depends on FUNCTION_TRACER
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.
48 tristate "Log panic/oops to a RAM buffer"
51 depends on HAVE_MEMBLOCK
53 select REED_SOLOMON_ENC8
54 select REED_SOLOMON_DEC8
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.
59 Note that for historical reasons, the module will be named
62 For more information, see Documentation/ramoops.txt.