All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Shivang Upadhyay <shivangu@linux.ibm.com>
Cc: sourabhjain@linux.ibm.com, kexec@lists.infradead.org
Subject: Re: [PATCH kexec-tools 0/4] ppc64: Support kexec with initrd and DTB together
Date: Tue, 11 Nov 2025 13:47:01 +0000	[thread overview]
Message-ID: <aRM-VWmxjXaqQvDC@horms.kernel.org> (raw)
In-Reply-To: <20251022134611.8921-1-shivangu@linux.ibm.com>

On Wed, Oct 22, 2025 at 07:16:05PM +0530, Shivang Upadhyay wrote:
> Currently, on ppc64 systems, kexec cannot directly use a
> user-provided devicetreeblob (dtb) when booting a new
> kernel with an initrd. This limitation exists because the
> dtb must be modified at runtime — for example, to include
> the initrd’s memory location and size, and to add
> /memreserve/ entries based on the current system memory
> layout.
> 
> Previously, kexec handled this by generating a fresh dtb in
> memory from the running system’s /proc/device-tree directory.
> However, this approach prevents users from making
> intentional modifications to the dtb — such as changin boot
> arguments, enabling or disabling devices, or testing kernel
> changes that depend on specific device tree properties.
> 
> Adding support for user-provided dtb (with appropriate
> patching by kexec) allows more control for developers,
> particularly when experimenting with custom kernels or
> hardware configurations.
> 
> This patch series lifts this restriction and ensures that
> the necessary /memreserve/ sections are properly added to
> the new DTB. on ppc64, it is mandatory, for the rebooting
> cpu to be present in the new kernel’s dtb, so additional
> logic has been added to identify and mark one of available
> cpu as reboot cpu on currect system.
> 
> A new architecture-specific function, arch_do_unload(), has
> been introduced to perform the necessary cleanup during
> kexec unload. in ppc64, the reboot CPU changes due to kexec,
> and it gets reset back on kexec unload.
> 
> Shivang Upadhyay (4):
>   ppc64: ensure /memreserve/ sections exist in user-provided FDT
>   ppc64: handle reboot CPU in case of user provided DTB
>   Add arch_do_unload hook for arch-specific cleanup
>   ppc64: life the dtb and initrd restriction

Thanks, applied.

- ppc64: life the dtb and initrd restriction
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=4dc039779675
- Add arch_do_unload hook for arch-specific cleanup
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=bf4aa2a1f365
- ppc64: handle reboot CPU in case of user provided DTB
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=39631c8fd64f
- ppc64: ensure /memreserve/ sections exist in user-provided FDT
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=32f664bfa479



  parent reply	other threads:[~2025-11-11 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 13:46 [PATCH kexec-tools 0/4] ppc64: Support kexec with initrd and DTB together Shivang Upadhyay
2025-10-22 13:46 ` [PATCH kexec-tools 1/4] ppc64: ensure /memreserve/ sections exist in user-provided FDT Shivang Upadhyay
2025-10-22 13:46 ` [PATCH kexec-tools 2/4] ppc64: handle reboot CPU in case of user provided DTB Shivang Upadhyay
2025-10-22 13:46 ` [PATCH kexec-tools 3/4] Add arch_do_unload hook for arch-specific cleanup Shivang Upadhyay
2025-10-22 13:46 ` [PATCH kexec-tools 4/4] ppc64: life the dtb and initrd restriction Shivang Upadhyay
2025-11-11 13:47 ` Simon Horman [this message]
2025-11-12 12:10   ` [PATCH kexec-tools 0/4] ppc64: Support kexec with initrd and DTB together Shivang Upadhyay

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=aRM-VWmxjXaqQvDC@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=kexec@lists.infradead.org \
    --cc=shivangu@linux.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.