From: Eugen Hristev <eugen.hristev@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-doc@vger.kernel.org, corbet@lwn.net, tglx@linutronix.de,
mingo@redhat.com, rostedt@goodmis.org, john.ogness@linutronix.de,
senozhatsky@chromium.org, pmladek@suse.com, peterz@infradead.org,
mojha@qti.qualcomm.com, linux-arm-kernel@lists.infradead.org,
vincent.guittot@linaro.org, konradybcio@kernel.org,
dietmar.eggemann@arm.com, juri.lelli@redhat.com
Subject: Re: [RFC][PATCH 00/14] introduce kmemdump
Date: Fri, 9 May 2025 18:19:40 +0300 [thread overview]
Message-ID: <26cc3478-8f65-44bb-8ebe-24a28a858dab@linaro.org> (raw)
In-Reply-To: <mtetvagzj2xltczutahqj7ijgpr3fy7ppbp5w6rmn2w2zmukux@tawhrkyoqjli>
Hello Bjorn,
On 5/7/25 19:54, Bjorn Andersson wrote:
> On Tue, Apr 22, 2025 at 02:31:42PM +0300, Eugen Hristev wrote:
>> kmemdump is a mechanism which allows the kernel to mark specific memory
>> areas for dumping or specific backend usage.
>> Once regions are marked, kmemdump keeps an internal list with the regions
>> and registers them in the backend.
>> Further, depending on the backend driver, these regions can be dumped using
>> firmware or different hardware block.
>> Regions being marked beforehand, when the system is up and running, there
>> is no need nor dependency on a panic handler, or a working kernel that can
>> dump the debug information.
>> The kmemdump approach works when pstore, kdump, or another mechanism do not.
>> Pstore relies on persistent storage, a dedicated RAM area or flash, which
>> has the disadvantage of having the memory reserved all the time, or another
>> specific non volatile memory. Some devices cannot keep the RAM contents on
>> reboot so ramoops does not work. Some devices do not allow kexec to run
>> another kernel to debug the crashed one.
>> For such devices, that have another mechanism to help debugging, like
>> firmware, kmemdump is a viable solution.
>>
>> kmemdump can create a core image, similar with /proc/vmcore, with only
>> the registered regions included. This can be loaded into crash tool/gdb and
>> analyzed.
>> To have this working, specific information from the kernel is registered,
>> and this is done at kmemdump init time, no need for the kmemdump user to
>> do anything.
>>
>> The implementation is based on the initial Pstore/directly mapped zones
>> published as an RFC here:
>> https://lore.kernel.org/all/20250217101706.2104498-1-eugen.hristev@linaro.org/
>>
>> The back-end implementation for qcom_smem is based on the minidump
>> patch series and driver written by Mukesh Ojha, thanks:
>> https://lore.kernel.org/lkml/20240131110837.14218-1-quic_mojha@quicinc.com/
>>
>> I appreciate the feedback on this series, I know it is a longshot, and there
>> is a lot to improve, but I hope I am on the right track.
>>
>> Thanks,
>> Eugen
>>
>> PS. Here is how crash tool reports the dump:
>>
>> KERNEL: /home/eugen/linux-minidump/vmlinux [TAINTED]
>> DUMPFILE: /home/eugen/eee
>
> Can you please describe the steps taken to get acquire/generate this
> file and how to invoke crash?
>
Thank you for looking into this.
Next week, on 16th of May, on Friday, there will be a talk related to
this patch series at Linaro Connect in Lisbon. In that talk I will also
show a demo in which all the process of acquiring the core dump and
crash will be covered.
I will be traveling the following days, if I get the time I will submit
the steps as a reply to this email, if not, then for sure I will submit
them after the talk in Lisbon.
Eugen
> Regards,
> Bjorn
>
>> CPUS: 8 [OFFLINE: 7]
>> DATE: Thu Jan 1 02:00:00 EET 1970
>> UPTIME: 00:00:28
>> NODENAME: qemuarm64
>> RELEASE: 6.14.0-rc5-next-20250303-00014-g011eb2aaf7b6-dirty
>> VERSION: #169 SMP PREEMPT Thu Apr 17 14:12:21 EEST 2025
>> MACHINE: aarch64 (unknown Mhz)
>> MEMORY: 0
>> PANIC: ""
>>
>> crash> log
>> [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd4b2]
>> [ 0.000000] Linux version 6.14.0-rc5-next-20250303-00014-g011eb2aaf7b6-dirty (eugen@eugen-station) (aarch64-none-linux-gnu-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614, GNU ld (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 2.42.0.20240614) #169 SMP PREEMPT Thu Apr 17 14:12:21 EEST 2025
>> [ 0.000000] KASLR enabled
>> [...]
>>
>> Eugen Hristev (14):
>> Documentation: add kmemdump
>> kmemdump: introduce kmemdump
>> kmemdump: introduce qcom-md backend driver
>> soc: qcom: smem: add minidump device
>> Documentation: kmemdump: add section for coreimage ELF
>> kmemdump: add coreimage ELF layer
>> printk: add kmsg_kmemdump_register
>> kmemdump: coreimage: add kmsg registration
>> genirq: add irq_kmemdump_register
>> kmemdump: coreimage: add irq registration
>> panic: add panic_kmemdump_register
>> kmemdump: coreimage: add panic registration
>> sched: add sched_kmemdump_register
>> kmemdump: coreimage: add sched registration
>>
>> Documentation/debug/index.rst | 17 ++
>> Documentation/debug/kmemdump.rst | 83 +++++
>> drivers/Kconfig | 2 +
>> drivers/Makefile | 2 +
>> drivers/debug/Kconfig | 39 +++
>> drivers/debug/Makefile | 5 +
>> drivers/debug/kmemdump.c | 197 ++++++++++++
>> drivers/debug/kmemdump_coreimage.c | 293 ++++++++++++++++++
>> drivers/debug/qcom_md.c | 467 +++++++++++++++++++++++++++++
>> drivers/soc/qcom/smem.c | 10 +
>> include/linux/irqnr.h | 1 +
>> include/linux/kmemdump.h | 77 +++++
>> include/linux/kmsg_dump.h | 6 +
>> include/linux/panic.h | 1 +
>> include/linux/sched.h | 1 +
>> kernel/irq/irqdesc.c | 7 +
>> kernel/panic.c | 8 +
>> kernel/printk/printk.c | 13 +
>> kernel/sched/core.c | 7 +
>> 19 files changed, 1236 insertions(+)
>> create mode 100644 Documentation/debug/index.rst
>> create mode 100644 Documentation/debug/kmemdump.rst
>> create mode 100644 drivers/debug/Kconfig
>> create mode 100644 drivers/debug/Makefile
>> create mode 100644 drivers/debug/kmemdump.c
>> create mode 100644 drivers/debug/kmemdump_coreimage.c
>> create mode 100644 drivers/debug/qcom_md.c
>> create mode 100644 include/linux/kmemdump.h
>>
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2025-05-09 15:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 11:31 Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 01/14] Documentation: add kmemdump Eugen Hristev
2025-05-09 17:31 ` Trilok Soni
2025-04-22 11:31 ` [RFC][PATCH 02/14] kmemdump: introduce kmemdump Eugen Hristev
2025-05-09 22:38 ` Bjorn Andersson
2025-04-22 11:31 ` [RFC][PATCH 03/14] kmemdump: introduce qcom-md backend driver Eugen Hristev
2025-05-09 23:21 ` Bjorn Andersson
2025-04-22 11:31 ` [RFC][PATCH 04/14] soc: qcom: smem: add minidump device Eugen Hristev
2025-05-07 16:56 ` Bjorn Andersson
2025-04-22 11:31 ` [RFC][PATCH 05/14] Documentation: kmemdump: add section for coreimage ELF Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 06/14] kmemdump: add coreimage ELF layer Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 07/14] printk: add kmsg_kmemdump_register Eugen Hristev
2025-05-05 15:25 ` Petr Mladek
2025-05-05 15:51 ` Eugen Hristev
2025-05-06 7:24 ` Petr Mladek
2025-04-22 11:31 ` [RFC][PATCH 08/14] kmemdump: coreimage: add kmsg registration Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 09/14] genirq: add irq_kmemdump_register Eugen Hristev
2025-05-07 10:18 ` Thomas Gleixner
2025-05-07 10:27 ` Eugen Hristev
2025-06-13 14:33 ` Eugen Hristev
2025-06-13 21:10 ` Thomas Gleixner
2025-06-16 10:12 ` Eugen Hristev
2025-06-17 8:33 ` Thomas Gleixner
2025-04-22 11:31 ` [RFC][PATCH 10/14] kmemdump: coreimage: add irq registration Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 11/14] panic: add panic_kmemdump_register Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 12/14] kmemdump: coreimage: add panic registration Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 13/14] sched: add sched_kmemdump_register Eugen Hristev
2025-04-22 11:31 ` [RFC][PATCH 14/14] kmemdump: coreimage: add sched registration Eugen Hristev
2025-04-23 7:04 ` [RFC][PATCH 00/14] introduce kmemdump Trilok Soni
2025-05-07 16:54 ` Bjorn Andersson
2025-05-09 15:19 ` Eugen Hristev [this message]
2025-06-02 8:46 ` Eugen Hristev
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=26cc3478-8f65-44bb-8ebe-24a28a858dab@linaro.org \
--to=eugen.hristev@linaro.org \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=john.ogness@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mojha@qti.qualcomm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
/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
all inboxes | Powered by JetHome®