From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: powerpc/kexec_file: print configured kernel command line
Date: Fri, 10 Jul 2026 09:10:54 +0530 [thread overview]
Message-ID: <zezzv7eh.ritesh.list@gmail.com> (raw)
In-Reply-To: <20250725124438.327593-1-sourabhjain@linux.ibm.com>
Sourabh Jain <sourabhjain@linux.ibm.com> writes:
> Kexec with the -d option prints extra logs about the kexec/kdump kernel
> that help debug kexec and kdump. For example, it shows what kexec
> segments are loaded, their locations, and sizes.
>
> One key piece of information still missing is the kernel command line
> configured for the kexec/kdump kernel.
>
> With this patch included, the kernel will print the kernel command line
> configured for the kexec/kdump kernel as shown below:
>
> kexec --initrd=./initrd ./kernel -lspd --command-line="test1 test2"
>
> Loaded elf core header at 0x22e30000, bufsz=0x2000 memsz=0x80000
> kexec_elf: Command line: elfcorehdr=0x22e30000 test1 test2 <--- New
> kexec_elf: Loaded initrd at 0x22eb0000
>
Looks like this slipped through the cracks. agreed that this is good to
have info. LGTM. So please feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
(this was still cleanly applicable on my latest dev tree)
> Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
-ritesh
next prev parent reply other threads:[~2026-07-10 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 12:44 powerpc/kexec_file: print configured kernel command line Sourabh Jain
2026-07-10 3:40 ` Ritesh Harjani [this message]
2026-07-10 7:05 ` Mukesh Kumar Chaurasiya
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=zezzv7eh.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sourabhjain@linux.ibm.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