From: "HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
To: Prasad Koya <prasad@arista.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: enhance makedumpfile to dump process list from vmcore
Date: Wed, 19 Jun 2024 05:44:56 +0000 [thread overview]
Message-ID: <56a5a42d-a2cd-4988-853f-49df60813ecb@nec.com> (raw)
In-Reply-To: <CAKh1g55PTX=tXoiQB8sKiZ1T+bBnCE4W67fFi5G8zEfh-nKq2g@mail.gmail.com>
On 2024/06/06 3:10, Prasad Koya wrote:
> Hi
>
> We use makedumpfile to read the dmesg buffer from the vmcore. We are
> working on adding a feature to makedumpfile to extract the "process
> list" from /proc/vmcore. Our main use case is to save the processes
> that were running at the time of kernel crash to a file on the
> permanent storage from the kdump kernel. We intend to read a handful
> of useful data for each running task: pid, parent pid, real parent
> pid, priority, nice value, RSS, VM size, command, utime, stime, OOM
> score.
>
> Process list from vmcore can probably be read using crash utility, but
> in our embedded system using makedumpfile to do that job makes sense
> for us.
>
> If such an option is useful for the general users of makedumpfile,
> we'd like to get more inputs and contribute to this feature.
Hi Prasad,
thank you for sharing the idea. But sorry, currently we are not
interested in implementing such a big function in makedumpfile.
The dmesg buffer is the most important information to be able to
determine the cause of a crash only with it, so the --dump-dmesg option
was implemented in makedumpfile first once upon a time. But now we have
handier vmcore-dmesg command in kexec-tools, so we don't intend to add
other functions to makedumpfile than making a dumpfile.
I'm not sure whether these are doable, but I would suggest a few ideas
instead:
- make e.g. vmcore-process-list command like vmcore-dmesg.
- use panic notifier to dump process list to the dmesg buffer before
kdump, and use vmcore-dmesg to get it.
Thanks,
Kazu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2024-06-19 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 18:10 enhance makedumpfile to dump process list from vmcore Prasad Koya
2024-06-19 5:44 ` HAGIO KAZUHITO(萩尾 一仁) [this message]
2024-06-24 1:52 ` Dave Young
2024-06-24 8:08 ` HAGIO KAZUHITO(萩尾 一仁)
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=56a5a42d-a2cd-4988-853f-49df60813ecb@nec.com \
--to=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=prasad@arista.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