From: Nicolas Schier <nsc@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Simon Glass" <sjg@chromium.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org,
"Sascha Hauer" <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2 2/2] kbuild: add target to build a cpio containing modules
Date: Wed, 26 Nov 2025 21:48:59 +0100 [thread overview]
Message-ID: <aSdnuxCNjwAma4_X@derry.ads.avm.de> (raw)
In-Reply-To: <20251125-cpio-modules-pkg-v2-2-aa8277d89682@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2781 bytes --]
On Tue, Nov 25, 2025 at 02:18:20PM +0100, Ahmad Fatoum wrote:
> From: Sascha Hauer <s.hauer@pengutronix.de>
>
> Add a new package target to build a cpio archive containing the kernel
> modules. This is particularly useful to supplement an existing initramfs
> with the kernel modules so that the root filesystem can be started with
> all needed kernel modules without modifying it.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Tested-by: Simon Glass <sjg@chromium.org>
> Co-developed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> scripts/Makefile.package | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/scripts/Makefile.package b/scripts/Makefile.package
> index 74bcb9e7f7a4516473481468a0fcf700c3bead33..83bfcf7cb09fd2d69b97e0c19a2b99c728835e8d 100644
> --- a/scripts/Makefile.package
> +++ b/scripts/Makefile.package
> @@ -189,6 +189,25 @@ tar-pkg: linux-$(KERNELRELEASE)-$(ARCH).tar
> tar%-pkg: linux-$(KERNELRELEASE)-$(ARCH).tar.% FORCE
> @:
>
> +# modules-cpio-pkg - generate an initramfs with the modules
> +# ---------------------------------------------------------------------------
> +
> +.tmp_modules_cpio: FORCE
> + $(Q)$(MAKE) -f $(srctree)/Makefile
> + $(Q)rm -rf $@
> + $(Q)$(MAKE) -f $(srctree)/Makefile INSTALL_MOD_PATH=$@ modules_install
Do you know why '-f $(srctree)/Makefile' is necessary here? As this
and the make call two lines above call common top-level targets, I do
not see the reason for explicitly adding the Makefile path. Am I
missing something; or have you observed problems without '-f'?
> +
> +quiet_cmd_cpio = CPIO $@
> + cmd_cpio = $(CONFIG_SHELL) $(srctree)/usr/gen_initramfs.sh -o $@ $<
> +
> +modules-$(KERNELRELEASE)-$(ARCH).cpio: .tmp_modules_cpio
> + $(Q)$(MAKE) $(build)=usr usr/gen_init_cpio
> + $(call cmd,cpio)
Removing the '$(MAKE) $(build)=usr usr/gen_init_cpio' line and adding
PHONY += usr_gen_init_cpio
usr_gen_init_cpio: scripts_basic
$(Q)$(MAKE) $(build)=usr usr/gen_init_cpio
modules-cpio-pkg: usr_gen_init_cpio
to top-level Makefile could be used to allow make to compile
gen_init_cpio in parallel instead of sequential. And it simplifies a
possible move of gen_init_cpio from usr/ to scripts/, as Nathan
suggested.
What do you think? (Top-level Makefile addition should probably better
be integrated into patch 1.) I can also send this as a follow-up patch
after merging your patches.
Nevertheless,
Tested-by: Nicolas Schier <nsc@kernel.org>
If there are no further remarks, I am going to merge the patch set
before the weekend.
Thanks and kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-11-26 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 13:18 [PATCH v2 0/2] kbuild: add target to build a cpio containing modules Ahmad Fatoum
2025-11-25 13:18 ` [PATCH v2 1/2] initramfs: add gen_init_cpio to hostprogs unconditionally Ahmad Fatoum
2025-11-25 22:15 ` Simon Glass
2025-11-25 13:18 ` [PATCH v2 2/2] kbuild: add target to build a cpio containing modules Ahmad Fatoum
2025-11-26 20:48 ` Nicolas Schier [this message]
2025-11-25 23:56 ` [PATCH v2 0/2] " Nathan Chancellor
2025-11-26 7:06 ` Thomas Weißschuh
2025-11-28 21:42 ` Nicolas Schier
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=aSdnuxCNjwAma4_X@derry.ads.avm.de \
--to=nsc@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sjg@chromium.org \
--cc=thomas.weissschuh@linutronix.de \
/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