Mukesh Ojha
1c4893edfe
There could be a scenario where we define some region
in normal memory and use them store to logs which is later
retrieved by bootloader during warm reset.
In this scenario, we wanted to treat this memory as normal
cacheable memory instead of default behaviour which
is an overhead. Making it cacheable could improve
performance.
This commit gives control to change mem_type from Device
tree, and also documents the value for normal memory.
Bug: 179108912
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
(cherry picked from commit 9d843e8faf
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore)
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/1616438537-13719-1-git-send-email-mojha@codeaurora.org
Change-Id: I56ae3c5dba729962854a5d590d8c80cc3aae12bd
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
67 lines
2.6 KiB
Plaintext
67 lines
2.6 KiB
Plaintext
Ramoops oops/panic logger
|
|
=========================
|
|
|
|
ramoops provides persistent RAM storage for oops and panics, so they can be
|
|
recovered after a reboot. This is a child-node of "/reserved-memory", and
|
|
is named "ramoops" after the backend, rather than "pstore" which is the
|
|
subsystem.
|
|
|
|
Parts of this storage may be set aside for other persistent log buffers, such
|
|
as kernel log messages, or for optional ECC error-correction data. The total
|
|
size of these optional buffers must fit in the reserved region.
|
|
|
|
Any remaining space will be used for a circular buffer of oops and panic
|
|
records. These records have a configurable size, with a size of 0 indicating
|
|
that they should be disabled.
|
|
|
|
At least one of "record-size", "console-size", "ftrace-size", or "pmsg-size"
|
|
must be set non-zero, but are otherwise optional as listed below.
|
|
|
|
|
|
Required properties:
|
|
|
|
- compatible: must be "ramoops"
|
|
|
|
- reg: region of memory that is preserved between reboots
|
|
|
|
|
|
Optional properties:
|
|
|
|
- ecc-size: enables ECC support and specifies ECC buffer size in bytes
|
|
(defaults to 0: no ECC)
|
|
|
|
- record-size: maximum size in bytes of each kmsg dump.
|
|
(defaults to 0: disabled)
|
|
|
|
- console-size: size in bytes of log buffer reserved for kernel messages
|
|
(defaults to 0: disabled)
|
|
|
|
- ftrace-size: size in bytes of log buffer reserved for function tracing and
|
|
profiling (defaults to 0: disabled)
|
|
|
|
- pmsg-size: size in bytes of log buffer reserved for userspace messages
|
|
(defaults to 0: disabled)
|
|
|
|
- mem-type: if present, sets the type of mapping is to be used to map the
|
|
reserved region. mem-type: 0 = write-combined (default), 1 = unbuffered,
|
|
2 = cached.
|
|
|
|
- unbuffered: deprecated, use mem_type instead. if present, and mem_type is
|
|
not specified, it is equivalent to mem_type = 1 and uses unbuffered mappings
|
|
to map the reserved region (defaults to buffered mappings mem_type = 0). If
|
|
both are specified -- "mem_type" overrides "unbuffered".
|
|
|
|
- max-reason: if present, sets maximum type of kmsg dump reasons to store
|
|
(defaults to 2: log Oopses and Panics). This can be set to INT_MAX to
|
|
store all kmsg dumps. See include/linux/kmsg_dump.h KMSG_DUMP_* for other
|
|
kmsg dump reason values. Setting this to 0 (KMSG_DUMP_UNDEF), means the
|
|
reason filtering will be controlled by the printk.always_kmsg_dump boot
|
|
param: if unset, it will be KMSG_DUMP_OOPS, otherwise KMSG_DUMP_MAX.
|
|
|
|
- no-dump-oops: deprecated, use max_reason instead. If present, and
|
|
max_reason is not specified, it is equivalent to max_reason = 1
|
|
(KMSG_DUMP_PANIC).
|
|
|
|
- flags: if present, pass ramoops behavioral flags (defaults to 0,
|
|
see include/linux/pstore_ram.h RAMOOPS_FLAG_* for flag values).
|