mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: linux-arm-kernel@lists.infradead.org
Cc: "Chen-Yu Tsai" <wenst@chromium.org>,
	"Ahmad Fatoum" <a.fatoum@pengutronix.de>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"J . Neuschäfer" <j.ne@posteo.net>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	"Tom Rini" <trini@konsulko.com>, "Simon Glass" <sjg@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/7] scripts/make_fit: Speed up operation
Date: Mon,  6 Oct 2025 17:01:52 -0600	[thread overview]
Message-ID: <20251006230205.521341-2-sjg@chromium.org> (raw)
In-Reply-To: <20251006230205.521341-1-sjg@chromium.org>

The kernel is likely at least 16MB so we may as well use that as a step
size when reallocating space for the FIT in memory. Pack the FIT at the
end, so there is no wasted space.

This reduces the time to pack by an order of magnitude, or so.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

(no changes since v3)

Changes in v3:
- Move the ramdisk chunk into the correct patch

 scripts/make_fit.py | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/scripts/make_fit.py b/scripts/make_fit.py
index 1683e5ec6e67..0f5e7c4b8aed 100755
--- a/scripts/make_fit.py
+++ b/scripts/make_fit.py
@@ -98,7 +98,7 @@ def setup_fit(fsw, name):
         fsw (libfdt.FdtSw): Object to use for writing
         name (str): Name of kernel image
     """
-    fsw.INC_SIZE = 65536
+    fsw.INC_SIZE = 16 << 20
     fsw.finish_reservemap()
     fsw.begin_node('')
     fsw.property_string('description', f'{name} with devicetree set')
@@ -299,7 +299,9 @@ def build_fit(args):
     finish_fit(fsw, entries)
 
     # Include the kernel itself in the returned file count
-    return fsw.as_fdt().as_bytearray(), seq + 1, size
+    fdt = fsw.as_fdt()
+    fdt.pack()
+    return fdt.as_bytearray(), seq + 1, size
 
 
 def run_make_fit():
-- 
2.43.0


  reply	other threads:[~2025-10-06 23:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 23:01 [PATCH v4 0/7] scripts/make_fit: Support ramdisks and faster operations Simon Glass
2025-10-06 23:01 ` Simon Glass [this message]
2025-11-08 21:14   ` [PATCH v4 1/7] scripts/make_fit: Speed up operation Nicolas Schier
2025-10-06 23:01 ` [PATCH v4 2/7] scripts/make_fit: Support an initial ramdisk Simon Glass
2025-11-08 21:15   ` Nicolas Schier
2025-10-06 23:01 ` [PATCH v4 3/7] scripts/make_fit: Move dtb processing into a function Simon Glass
2025-11-08 21:15   ` Nicolas Schier
2025-10-06 23:01 ` [PATCH v4 4/7] scripts/make_fit: Provide a way to add built modules Simon Glass
2025-11-08 21:16   ` Nicolas Schier
2025-11-14 18:09     ` Simon Glass
2025-10-06 23:01 ` [PATCH v4 5/7] kbuild: Allow adding modules into the FIT ramdisk Simon Glass
2025-11-08 21:17   ` Nicolas Schier
2025-11-14 14:29     ` Simon Glass
2025-10-06 23:01 ` [PATCH v4 6/7] scripts/make_fit: Support a few more parallel compressors Simon Glass
2025-10-06 23:01 ` [PATCH v4 7/7] scripts/make_fit: Compress dtbs in parallel Simon Glass
2025-10-30 17:48 ` [PATCH v4 0/7] scripts/make_fit: Support ramdisks and faster operations Simon Glass

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=20251006230205.521341-2-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=a.fatoum@pengutronix.de \
    --cc=j.ne@posteo.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=trini@konsulko.com \
    --cc=wenst@chromium.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

all inboxes | Powered by JetHome®