2 tristate "Persistent store support"
5 This option enables generic access to platform level
6 persistent storage via "pstore" filesystem that can
7 be mounted as /dev/pstore. Only useful if you have
8 a platform level driver that registers with pstore to
9 provide the data, so you probably should just go say "Y"
10 (or "M") to a platform specific persistent store driver
11 (e.g. ACPI_APEI on X86) which will select this for you.
12 If you don't have a platform persistent store driver,
16 prompt "Choose compression algorithm"
18 default PSTORE_ZLIB_COMPRESS
20 This option chooses compression algorithm.
22 config PSTORE_ZLIB_COMPRESS
27 This option enables ZLIB compression algorithm support.
29 config PSTORE_LZO_COMPRESS
34 This option enables LZO compression algorithm support.
36 config PSTORE_LZ4_COMPRESS
41 This option enables LZ4 compression algorithm support.
45 bool "Log kernel console messages"
48 When the option is enabled, pstore will log all kernel
49 messages, even if no oops or panic happened.
52 bool "Log user space messages"
56 When the option is enabled, pstore will export a character
57 interface /dev/pmsg0 to log user space messages. On reboot
58 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID].
63 bool "Persistent function tracer"
65 depends on FUNCTION_TRACER
68 With this option kernel traces function calls into a persistent
69 ram buffer that can be decoded and dumped after reboot through
70 pstore filesystem. It can be used to determine what function
71 was last called before a reset or panic.
76 tristate "Log panic/oops to a RAM buffer"
79 depends on HAVE_MEMBLOCK
81 select REED_SOLOMON_ENC8
82 select REED_SOLOMON_DEC8
84 This enables panic and oops messages to be logged to a circular
85 buffer in RAM where it can be read back at some later point.
87 Note that for historical reasons, the module will be named
90 For more information, see Documentation/admin-guide/ramoops.rst.