From: Frediano Ziglio <frediano.ziglio@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: "Frediano Ziglio" <frediano.ziglio@cloud.com>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Jan Beulich" <jbeulich@suse.com>
Subject: [PATCH v2 0/2] xen/efi: Make boot more flexible, especially with GRUB2
Date: Tue, 24 Jun 2025 15:27:07 +0100 [thread overview]
Message-ID: <20250624142711.54925-1-frediano.ziglio@cloud.com> (raw)
The combination of GRUB2, EFI and UKI allows potentially more flexibility.
For instance is possible to load xen.efi from a no ESP partition leaving
a boot loader like GRUB2 taking care of the file loading.
This however requires some changes in Xen to be less restrictive.
Specifically for GRUB2 these changes allows the usage of "chainloader"
command with UKI and reading xen.efi from no ESP (so no DeviceHandle
set) and usage of "linux" and "initrd" commands to load separately
the kernel (embedding using UKI) and initrd (using LoadFile2 protocol).
Changes since v1:
- keep read_file fatal when it was so;
- attempt to use LoadFile2 after trying object section;
- minor changes (see details on specific changes).
Frediano Ziglio (2):
xen/efi: Handle cases where file didn't come from ESP
xen/efi: Support loading initrd using GRUB2 LoadFile2 protocol
xen/common/efi/boot.c | 105 +++++++++++++++++++++++++++++++++++---
xen/include/efi/efidevp.h | 21 ++++++++
2 files changed, 120 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2025-06-24 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 14:27 Frediano Ziglio [this message]
2025-06-24 14:27 ` [PATCH v2 1/2] xen/efi: Handle cases where file didn't come from ESP Frediano Ziglio
2025-06-24 14:39 ` Marek Marczykowski-Górecki
2025-06-24 14:27 ` [PATCH v2 2/2] xen/efi: Support loading initrd using GRUB2 LoadFile2 protocol Frediano Ziglio
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=20250624142711.54925-1-frediano.ziglio@cloud.com \
--to=frediano.ziglio@cloud.com \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xenproject.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.