Currently, ramoops is capable to collect dmesg buffer only during
panic and oops events. However, it is desirable for shutdown performance
analysis reasons to optionally allow collecting dmesg buffers during other
events as well: reboot, kexec, emergency reboot etc.
How to quickly test:
virtme-run --mods=auto --kdir --mods=auto --kdir . \
-a memmap=1G$8G -a ramoops.mem_address=0x200000000 \
-a ramoops.mem_size=0x100000 -a ramoops.record_size=32768 \
-a ramoops.dump_all=1 -a quiet --qemu-opts -m 8G
..
# reboot -f
After VM is back:
# mount -t pstore pstore /mnt
# head /mnt/dmesg-ramoops-0
Restart#1 Part1
...
Pavel Tatashin (3):
printk: honor the max_reason field in kmsg_dumper
pstore/ram: allow to dump kmesg during regular reboot
ramoops: add dump_all optional field to ramoops DT node
.../bindings/reserved-memory/ramoops.txt | 3 ++
fs/pstore/platform.c | 6 ++-
fs/pstore/ram.c | 38 +++++++++++++------
include/linux/kmsg_dump.h | 1 +
include/linux/pstore.h | 1 +
include/linux/pstore_ram.h | 1 +
kernel/printk/printk.c | 16 ++++----
7 files changed, 46 insertions(+), 20 deletions(-)
--
2.25.1
