From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Gerald Elder-Vass" <gerald.elder-vass@cloud.com>,
xen-devel@lists.xenproject.org, dpsmith@apertussolutions.com,
"Frediano Ziglio" <frediano.ziglio@cloud.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [XEN PATCH v3] sbat: Add SBAT section to the Xen EFI binary
Date: Thu, 8 May 2025 12:31:40 +0200 [thread overview]
Message-ID: <aByIDP2iEHjmo99t@mail-itl> (raw)
In-Reply-To: <94652153-99fe-47d8-84d5-cbf2865ad6e0@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
On Thu, May 08, 2025 at 09:51:59AM +0100, Andrew Cooper wrote:
> Also,
>
> > ld: warning: orphan section `.sbat' from `prelink.o' being placed in section `.sbat'
>
> This is because sbat.o is getting linked into the non-EFI build of Xen too.
>
> I'm less sure how to go about fixing this. There's no nice way I can
> see of of getting sbat.o only in the EFI build. The other option is to
> discard it for the ELF build.
This is kinda related to my question on Matrix - is multiboot2 binary
also supposed to (eventually) support UEFI SB?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-08 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 13:54 [XEN PATCH v3] sbat: Add SBAT section to the Xen EFI binary Gerald Elder-Vass
2025-05-08 8:51 ` Andrew Cooper
2025-05-08 10:31 ` Marek Marczykowski-Górecki [this message]
2025-05-08 11:55 ` Andrew Cooper
2025-05-08 12:28 ` Frediano Ziglio
2025-05-08 12:43 ` Marek Marczykowski-Górecki
2025-05-08 10:46 ` Frediano Ziglio
2025-05-12 10:50 ` Jan Beulich
2025-05-12 11:26 ` Andrew Cooper
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=aByIDP2iEHjmo99t@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=frediano.ziglio@cloud.com \
--cc=gerald.elder-vass@cloud.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.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.