From: Ard Biesheuvel <ardb+git@google.com>
To: linux-efi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
will@kernel.org, catalin.marinas@arm.com,
Ard Biesheuvel <ardb@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: [PATCH 0/5] efi: Expose loaded image properties via info struct
Date: Fri, 6 Nov 2026 15:19:37 +0100 [thread overview]
Message-ID: <20261106141936.2744481-7-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Clean up the arm64 build script and linker hacks that zboot uses to
obtain properties of the loaded image (which it cannot access directly
via a relative reference like the ordinary EFI stub).
Instead, define a struct efi_image_info (whose contents are arch
specific), and expose its offset in the loaded image via the arm64 image
header, so that zboot can access it after decompressing the image.
Cc: Jason Gunthorpe <jgg@nvidia.com>
Link: https://lore.kernel.org/all/0-v2-989a18390eb1+486-arm64_drtm_jgg@nvidia.com/
Ard Biesheuvel (5):
efi/libstub: Make efi_remap_image() return efi_status_t
efi/libstub: Pass a struct efi_image_info to efi_stub_common()
efi/zboot: Disentangle efi_remap_image() from efi_cache_sync_image()
efi/arm64: Expose struct efi_image_info via the image header
efi/arm64: Drop build and linker script hacks to obtain image code
size
Documentation/arch/arm64/booting.rst | 3 +-
arch/arm64/boot/Makefile | 3 --
arch/arm64/include/asm/efi.h | 11 ++++++
arch/arm64/include/asm/image.h | 4 ++-
arch/arm64/kernel/efi-header.S | 6 ++++
arch/arm64/kernel/head.S | 3 +-
arch/arm64/kernel/image-vars.h | 4 ---
drivers/firmware/efi/libstub/arm64-stub.c | 16 +++++++++
drivers/firmware/efi/libstub/arm64.c | 13 ++++---
drivers/firmware/efi/libstub/efi-stub-entry.c | 8 ++++-
drivers/firmware/efi/libstub/efi-stub-helper.c | 13 ++++---
drivers/firmware/efi/libstub/efi-stub.c | 3 +-
drivers/firmware/efi/libstub/efistub.h | 16 +++++++--
drivers/firmware/efi/libstub/zboot.c | 36 ++++++++++++++++++--
drivers/firmware/efi/libstub/zboot.lds | 7 ----
15 files changed, 112 insertions(+), 34 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.56.0.455.g6c5a503b38-goog
next reply other threads:[~2026-11-06 14:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 14:19 Ard Biesheuvel [this message]
2026-11-06 14:19 ` [PATCH 1/5] efi/libstub: Make efi_remap_image() return efi_status_t Ard Biesheuvel
2026-11-06 14:36 ` sashiko-bot
2026-11-06 14:19 ` [PATCH 2/5] efi/libstub: Pass a struct efi_image_info to efi_stub_common() Ard Biesheuvel
2026-11-06 14:27 ` sashiko-bot
2026-11-06 14:19 ` [PATCH 3/5] efi/zboot: Disentangle efi_remap_image() from efi_cache_sync_image() Ard Biesheuvel
2026-11-06 14:34 ` sashiko-bot
2026-11-06 14:19 ` [PATCH 4/5] efi/arm64: Expose struct efi_image_info via the image header Ard Biesheuvel
2026-11-06 14:34 ` Jason Gunthorpe
2026-11-06 15:51 ` Ard Biesheuvel
2026-11-06 17:09 ` Jason Gunthorpe
2026-11-06 14:19 ` [PATCH 5/5] efi/arm64: Drop build and linker script hacks to obtain image code size Ard Biesheuvel
2026-11-06 14:33 ` sashiko-bot
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=20261106141936.2744481-7-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jgg@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@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 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.