1config PSTORE 2 bool "Persistent store support" 3 default n 4 help 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, 13 say N. 14 15config PSTORE_CONSOLE 16 bool "Log kernel console messages" 17 depends on PSTORE 18 help 19 When the option is enabled, pstore will log all kernel 20 messages, even if no oops or panic happened. 21 22config PSTORE_PMSG 23 bool "Log user space messages" 24 depends on PSTORE 25 help 26 When the option is enabled, pstore will export a character 27 interface /dev/pmsg0 to log user space messages. On reboot 28 data can be retrieved from /sys/fs/pstore/pmsg-ramoops-[ID]. 29 30 If unsure, say N. 31 32config PSTORE_FTRACE 33 bool "Persistent function tracer" 34 depends on PSTORE 35 depends on FUNCTION_TRACER 36 depends on DEBUG_FS 37 help 38 With this option kernel traces function calls into a persistent 39 ram buffer that can be decoded and dumped after reboot through 40 pstore filesystem. It can be used to determine what function 41 was last called before a reset or panic. 42 43 If unsure, say N. 44 45config PSTORE_RAM 46 tristate "Log panic/oops to a RAM buffer" 47 depends on PSTORE 48 depends on HAS_IOMEM 49 depends on HAVE_MEMBLOCK 50 select REED_SOLOMON 51 select REED_SOLOMON_ENC8 52 select REED_SOLOMON_DEC8 53 help 54 This enables panic and oops messages to be logged to a circular 55 buffer in RAM where it can be read back at some later point. 56 57 Note that for historical reasons, the module will be named 58 "ramoops.ko". 59 60 For more information, see Documentation/ramoops.txt. 61