From: Ard Biesheuvel <ardb@kernel.org>
To: grub-devel@gnu.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
Daniel Kiper <daniel.kiper@oracle.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Nikita Ermakov <arei@altlinux.org>,
Atish Patra <atishp@atishpatra.org>,
Huacai Chen <chenhuacai@loongson.cn>,
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
dann frazier <dann.frazier@canonical.com>,
Julian Andres Klode <julian.klode@canonical.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: [PATCH v5 0/6] linux: implement LoadFile2 initrd loading
Date: Tue, 18 Oct 2022 21:05:01 +0200 [thread overview]
Message-ID: <20221018190508.177568-1-ardb@kernel.org> (raw)
This implements the LoadFile2 initrd loading protocol, which is
essentially a callback interface into the bootloader to load the initrd
data into a caller provided buffer. This means the bootloader no longer
has to contain any policy regarding where to load the initrd (which
differs between architectures and kernel versions) and no longer has to
manipulate arch specific data structures such as DT or struct bootparams
to inform the OS where the initrd resides in memory. This is especially
relevant for the upcoming LoongArch support, which does not use either
DT or struct bootparams, and would have to rely on the initrd= command
line interface, which is deprecated and of limited utility [0].
Sample output from booting a recent Linux/arm64 kernel:
grub> insmod part_msdos
grub> linux (hd0,msdos1)/Image
grub> initrd (hd0,msdos1)/initrd.img
grub> boot
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable
EFI stub: Generating empty DTB
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd070]
Changes since v4:
- incorporate review feedback from Daniel regarding whitespace and other
minor style deviations
Changes since v3:
- drop a couple of patches that have been merged independently in the
meantime
- update patch #1 to read the PE image header offset from the file
instead of using the harcoded offset
- add acks from Heinrich and Ilias
Changes since v2:
- incorporate some ancient feedback from Daniel that I never saw until
today. (this is why I am sending two versions of the same series on
the same day - apologies for the spam)
[0] The initrd= command line loader can only access files that reside on
the same volume as the loaded image, which means GRUB would have to
present this volume abstraction in order to serve the initrd file.
Cc: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Nikita Ermakov <arei@altlinux.org>
Cc: Atish Patra <atishp@atishpatra.org>
Cc: Huacai Chen <chenhuacai@loongson.cn>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: dann frazier <dann.frazier@canonical.com>
Cc: Julian Andres Klode <julian.klode@canonical.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Ard Biesheuvel (6):
efi: move MS-DOS stub out of generic PE header definition
linux/arm: unify ARM/arm64 vs Xen PE/COFF header handling
linux/arm: account for COFF headers appearing at unexpected offsets
efi/efinet: Don't close connections at fini_hw() time
efi: implement LoadFile2 initrd loading protocol for Linux
linux: ignore FDT unless we need to modify it
grub-core/commands/efi/lsefi.c | 1 +
grub-core/kern/efi/efi.c | 8 +-
grub-core/loader/arm64/linux.c | 173 ++++++++++++++++++--
grub-core/loader/arm64/xen_boot.c | 23 +--
grub-core/loader/efi/fdt.c | 7 +-
grub-core/net/drivers/efi/efinet.c | 10 +-
grub-core/net/net.c | 2 +-
include/grub/arm/linux.h | 5 +
include/grub/arm64/linux.h | 2 +
include/grub/efi/api.h | 40 +++++
include/grub/efi/efi.h | 4 +-
include/grub/efi/pe32.h | 16 +-
include/grub/net.h | 3 +-
13 files changed, 246 insertions(+), 48 deletions(-)
--
2.35.1
next reply other threads:[~2022-10-18 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:05 Ard Biesheuvel [this message]
2022-10-18 19:05 ` [PATCH v5 1/6] efi: move MS-DOS stub out of generic PE header definition Ard Biesheuvel
2022-10-18 19:05 ` [PATCH v5 2/6] linux/arm: unify ARM/arm64 vs Xen PE/COFF header handling Ard Biesheuvel
2022-10-18 19:05 ` [PATCH v5 3/6] linux/arm: account for COFF headers appearing at unexpected offsets Ard Biesheuvel
2022-10-18 19:05 ` [PATCH v5 4/6] efi/efinet: Don't close connections at fini_hw() time Ard Biesheuvel
2022-10-18 19:05 ` [PATCH v5 5/6] efi: implement LoadFile2 initrd loading protocol for Linux Ard Biesheuvel
2022-10-18 19:05 ` [PATCH v5 6/6] linux: ignore FDT unless we need to modify it Ard Biesheuvel
2022-10-21 12:50 ` [PATCH v5 0/6] linux: implement LoadFile2 initrd loading Daniel Kiper
2022-10-21 13:15 ` Ard Biesheuvel
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=20221018190508.177568-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=arei@altlinux.org \
--cc=atishp@atishpatra.org \
--cc=chenhuacai@loongson.cn \
--cc=daniel.kiper@oracle.com \
--cc=dann.frazier@canonical.com \
--cc=grub-devel@gnu.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=julian.klode@canonical.com \
--cc=quic_llindhol@quicinc.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.