From: Ruipeng Qi <ruipengqi7@gmail.com>
To: catalin.marinas@arm.com, will@kernel.org, bhe@redhat.com,
vgoyal@redhat.com, dyoung@redhat.com,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Cc: zalbassam@google.com, dianders@chromium.org,
mark.rutland@arm.com, lecopzer.chen@mediatek.com, maz@kernel.org,
arnd@arndb.de, yury.norov@gmail.com, brauner@kernel.org,
mcgrof@kernel.org, maninder1.s@samsung.com,
michael.christie@oracle.com, samitolvanen@google.com,
linux-arm-kernel@lists.infradead.org, qiruipeng@lixiang.com
Subject: [RFC PATCH 0/7] osdump: Add one new os minidump module
Date: Thu, 21 Dec 2023 21:05:55 +0800 [thread overview]
Message-ID: <20231221130555.32551-1-ruipengqi7@gmail.com> (raw)
From: qiruipeng <qiruipeng@lixiang.com>
Osdump is a new crash dumping solution aiming at specific embedded
devices within automotive or Industrial.
- limited memory.
- reboot as soon as possible when system fault.
In order to reduce dump file size and speed up dump process, it has the
following features:
- no userspace memory, just designed for solving os issues.
- no const data, such as text segment
- dump core os data only.
- bss, data segments which alloc static.
- dynamic data
- slub data for little size data.
- some large size data.
- compress dump data to reduce dump file size.
consist of large massive of uncontinuous data,so use binary data format
directly.
reasemble a standard elf format file with dump file and vmlinux, and
then parse it with crash tool.
Signed-off-by: qiruipeng <qiruipeng@lixiang.com>
qiruipeng (7):
[RFC PATCH 1/7] osdump: Add one new os minidump module
[RFC PATCH 2/7] osdump: reuse some code from crash_core to get
vmcoreinfo
[RFC PATCH 3/7] doc: Add osdump guide
[RFC PATCH 4/7] dt-bindings: reserved-memory: Support osdump module
[RFC PATCH 5/7] sched: access to runqueues by function
[RFC PATCH 6/7] mm/slub: make slab data more observable
[RFC PATCH 7/7] panic: invoke osdump when panic
Documentation/admin-guide/index.rst | 1 +
Documentation/admin-guide/osdump.rst | 94 +++
.../bindings/reserved-memory/osdump.yaml | 45 ++
arch/arm64/Kconfig | 169 +++++
arch/arm64/kernel/Makefile | 1 +
drivers/of/platform.c | 1 +
include/linux/buildid.h | 3 +-
include/linux/osdump.h | 7 +
kernel/Makefile | 2 +
kernel/crash_core_mini.c | 275 ++++++++
kernel/osdump/Makefile | 1 +
kernel/osdump/compr.c | 252 ++++++++
kernel/osdump/core.c | 608 ++++++++++++++++++
kernel/osdump/extern.h | 13 +
kernel/osdump/inode.c | 77 +++
kernel/osdump/internal.h | 95 +++
kernel/panic.c | 7 +
kernel/printk/printk.c | 2 +-
kernel/sched/core.c | 8 +
lib/buildid.c | 3 +-
mm/slab.h | 2 +
mm/slub.c | 38 +-
22 files changed, 1700 insertions(+), 4 deletions(-)
create mode 100644 Documentation/admin-guide/osdump.rst
create mode 100644 Documentation/devicetree/bindings/reserved-memory/osdump.yaml
create mode 100644 include/linux/osdump.h
create mode 100644 kernel/crash_core_mini.c
create mode 100644 kernel/osdump/Makefile
create mode 100644 kernel/osdump/compr.c
create mode 100644 kernel/osdump/core.c
create mode 100644 kernel/osdump/extern.h
create mode 100644 kernel/osdump/inode.c
create mode 100644 kernel/osdump/internal.h
--
2.17.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
reply other threads:[~2023-12-21 13:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20231221130555.32551-1-ruipengqi7@gmail.com \
--to=ruipengqi7@gmail.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=brauner@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dianders@chromium.org \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mcgrof@kernel.org \
--cc=michael.christie@oracle.com \
--cc=qiruipeng@lixiang.com \
--cc=samitolvanen@google.com \
--cc=vgoyal@redhat.com \
--cc=will@kernel.org \
--cc=yury.norov@gmail.com \
--cc=zalbassam@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).