Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Joseph Cathcart <josephc@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, kexec@lists.infradead.org,
	eoin.mcnamara@ibm.com, iii@de.ibm.com
Subject: Re: [PATCH v2] kexec-tools/s390: add --reuseinitrd support
Date: Mon, 5 Oct 2026 10:25:26 +0100	[thread overview]
Message-ID: <20261005092526.GE184916@horms.kernel.org> (raw)
In-Reply-To: <20260820101350.4413-1-josephc@linux.ibm.com>

On Thu, Aug 20, 2026 at 12:13:50PM +0200, Joseph Cathcart wrote:
> Currently, the --reuseinitrd param is not supported on s390. This
> prevents testing kexec in environments such as virtme-ng, which by
> default does not store the initrd on disk.
> 
> When --reuseinitrd is specified, fetch retained initrd memory range
> from /proc/iomem and fill new kernel parmarea directly with retained
> initrd base and size, rather than memory range of a new ramdisk.
> 
> Add die() cases for when user uses --reuseinitrd:
>         - in addition to --ramdisk or --initrd
>         - while booting a crash kernel.
>         - with kexec-file-load syscall (default syscall)
>         - and no initrd entry is found in /proc/iomem
> 
> Signed-off-by: Joseph Cathcart <josephc@linux.ibm.com>

Sorry if this is a duplicate.
But it seems that I applied this patch some time ago
but forgot to send out a notification about that.

So, FTR, this patch was applied as:

- kexec-tools/s390: add --reuseinitrd support
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=43c5cba85ad2


      reply	other threads:[~2026-10-05  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 10:13 [PATCH v2] kexec-tools/s390: add --reuseinitrd support Joseph Cathcart
2026-10-05  9:25 ` Simon Horman [this message]

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=20261005092526.GE184916@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=eoin.mcnamara@ibm.com \
    --cc=iii@de.ibm.com \
    --cc=josephc@linux.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-s390@vger.kernel.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