From: Pavel Tatashin <pasha.tatashin@soleen.com>
To: pasha.tatashin@soleen.com, jmorris@namei.org, sashal@kernel.org,
linux-kernel@vger.kernel.org, pmladek@suse.com,
sergey.senozhatsky@gmail.com, rostedt@goodmis.org,
keescook@chromium.org, anton@enomsg.org, ccross@android.com,
tony.luck@intel.com, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/5] allow ramoops to collect all kmesg_dump events
Date: Tue, 5 May 2020 11:45:05 -0400 [thread overview]
Message-ID: <20200505154510.93506-1-pasha.tatashin@soleen.com> (raw)
pstore /mnt/console-ramoops-0 outputs only messages below the console
loglevel, and our console loglevel is set to 3 due to slowness of
serial console. Which means only errors and worse types of messages
are recorded. There is no way to have different log levels for
different consoles.
This patch series adds a new option to ramoops: max_reason that enables
it to collect kmdesg dumps for other reasons beside oops and panics.
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.max_reason=5 -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
...
Changelog:
v1:
https://lore.kernel.org/lkml/20200502143555.543636-1-pasha.tatashin@soleen.com
v2:
Addressed comments from Kees Cook, Steven Rostedt, and Sergey Senozhatsky
- Replaced dump_all with max_reason
- removed duplicated enum value
- moved always_kmsg_dump logic back to kmsg_dump().
Pavel Tatashin (5):
printk: honor the max_reason field in kmsg_dumper
pstore/platform: pass max_reason to kmesg dump
pstore/ram: in ramoops_platform_data convert dump_oops to max_reason
pstore/ram: allow to dump kmesg during regular reboot
ramoops: add max_reason optional field to ramoops DT node
Documentation/admin-guide/ramoops.rst | 11 +++---
.../bindings/reserved-memory/ramoops.txt | 10 ++++--
drivers/platform/chrome/chromeos_pstore.c | 2 +-
fs/pstore/platform.c | 4 ++-
fs/pstore/ram.c | 35 +++++++++----------
include/linux/kmsg_dump.h | 1 +
include/linux/pstore.h | 3 ++
include/linux/pstore_ram.h | 2 +-
kernel/printk/printk.c | 15 +++++---
9 files changed, 51 insertions(+), 32 deletions(-)
--
2.25.1
next reply other threads:[~2020-05-05 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 15:45 Pavel Tatashin [this message]
2020-05-05 15:45 ` [PATCH v2 1/5] printk: honor the max_reason field in kmsg_dumper Pavel Tatashin
2020-05-14 8:49 ` Petr Mladek
2020-05-05 15:45 ` [PATCH v2 2/5] pstore/platform: pass max_reason to kmesg dump Pavel Tatashin
2020-05-05 21:59 ` Kees Cook
2020-05-06 13:52 ` Steven Rostedt
2020-05-06 14:31 ` Pavel Tatashin
2020-05-06 14:42 ` Pavel Tatashin
2020-05-05 15:45 ` [PATCH v2 3/5] pstore/ram: in ramoops_platform_data convert dump_oops to max_reason Pavel Tatashin
2020-05-05 23:15 ` Kees Cook
2020-05-06 13:42 ` Pavel Tatashin
2020-05-05 15:45 ` [PATCH v2 4/5] pstore/ram: allow to dump kmesg during regular reboot Pavel Tatashin
2020-05-05 15:45 ` [PATCH v2 5/5] ramoops: add max_reason optional field to ramoops DT node Pavel Tatashin
2020-05-13 2:42 ` Rob Herring
2020-05-13 14:21 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200505154510.93506-1-pasha.tatashin@soleen.com \
--to=pasha.tatashin@soleen.com \
--cc=anton@enomsg.org \
--cc=ccross@android.com \
--cc=devicetree@vger.kernel.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=robh+dt@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).