public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com, jan.kiszka@siemens.com
Subject: Re: [PATCH v3 0/8] Add support to cross-compile a dracut initramfs
Date: Wed, 30 Sep 2026 12:42:10 +0200	[thread overview]
Message-ID: <52ecea35-159a-4be9-ba84-34d188bda79c@ilbers.de> (raw)
In-Reply-To: <20260925073042.1737353-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Zhihang

On 9/25/26 09:30, 'Felix Moessbauer' via isar-users wrote:
> Not a trivial change, but one that really pays off: On some real-world
> (non native) use cases the initrd generation takes more than 10 minutes.
> This is due to emulating the ldd, as well as the cpio and compression
> stages. With initramfs tools or the initramfs-tools wrapped dracut, we
> don't see any possibility to significantly speed up the process (and
> cross-building is also not supported). However, with direct invocation
> of dracut, cross-compiling the initramfs becomes feasible and significantly
> faster (on some cases more than 5x). This is especially relevant for
> initrd-only images, where the slow build times are already a blocker as
> of today.
>
> In combination with host-apt based package installation (not part of this
> series), this can cut the overall buildtime by a factor of 3x or more.
>
> Note, that isar-cip-core will soon profit from this change as well, as
> they plan to switch all initrd scripts to dracut.
>
> Changes since v2:
>
> - correctly unmount the host-tooling chroot (only relevant on privileged)
>
> Changes since v1:
>
> - make dependency to host tooling chroot more precise:
>    on external initrd bind it to the do_generate_initramfs task
>    on internal initrd bind it to the do_rootfs_install task
> - rebased onto next
>
> No other changes.
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (8):
>    rootfs: generalize deployment of rootfs artifact
>    dracut-module: make module-setup compatible with sysroot
>    initramfs: move dracut logic to initrd-dracut class
>    dracut: use fixed log level on generation for progress reporting
>    dracut: enforce build of reproducible initrd
>    add host-tooling chroot for generic host tooling
>    dracut: add support for cross initrd generation
>    rootfs: stub both dracut and update-initramfs on dracut
>
>   .../dracut-example-lighttpd/files/install.sh  | 12 ++--
>   .../recipes-initramfs/images/isar-dracut.bb   |  4 +-
>   meta/classes-recipe/host-tooling.bbclass      | 14 ++++
>   meta/classes-recipe/imagetypes_wic.bbclass    |  2 +-
>   meta/classes-recipe/initramfs.bbclass         |  2 +
>   meta/classes-recipe/initrd-dracut.bbclass     | 43 +++++++++++-
>   meta/classes-recipe/rootfs-deploy.bbclass     | 30 +++++++++
>   meta/classes-recipe/rootfs.bbclass            | 39 +++++++----
>   meta/classes/sbom.bbclass                     |  2 +-
>   meta/lib/rootfs_progress.py                   |  3 +-
>   .../dracut-cross-ldd/dracut-cross-ldd.bb      | 16 +++++
>   .../dracut-cross-ldd/files/dracut-cross-ldd   | 65 +++++++++++++++++++
>   .../host-tooling-chroot.bb                    | 28 ++++++++
>   .../sbom-chroot/sbom-chroot.bb                | 19 ++----
>   .../sbuild-chroot/sbuild-chroot.inc           | 30 ++-------
>   .../dracut-module/files/module-setup.sh.tmpl  |  2 +-
>   16 files changed, 251 insertions(+), 60 deletions(-)
>   create mode 100644 meta/classes-recipe/host-tooling.bbclass
>   create mode 100644 meta/classes-recipe/rootfs-deploy.bbclass
>   create mode 100644 meta/recipes-devtools/dracut-cross-ldd/dracut-cross-ldd.bb
>   create mode 100644 meta/recipes-devtools/dracut-cross-ldd/files/dracut-cross-ldd
>   create mode 100644 meta/recipes-devtools/host-tooling-chroot/host-tooling-chroot.bb
>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/52ecea35-159a-4be9-ba84-34d188bda79c%40ilbers.de.

      parent reply	other threads:[~2026-09-30 10:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25  7:30 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 1/8] rootfs: generalize deployment of rootfs artifact 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 2/8] dracut-module: make module-setup compatible with sysroot 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 3/8] initramfs: move dracut logic to initrd-dracut class 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 4/8] dracut: use fixed log level on generation for progress reporting 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 5/8] dracut: enforce build of reproducible initrd 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 6/8] add host-tooling chroot for generic host tooling 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 7/8] dracut: add support for cross initrd generation 'Felix Moessbauer' via isar-users
2026-09-25  7:30 ` [PATCH v3 8/8] rootfs: stub both dracut and update-initramfs on dracut 'Felix Moessbauer' via isar-users
2026-09-30 10:42 ` Zhihang Wei [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=52ecea35-159a-4be9-ba84-34d188bda79c@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=quirin.gylstorff@siemens.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