From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Frediano Ziglio <freddy77@gmail.com>
Cc: xen-devel@lists.xenproject.org,
"Daniel P. Smith" <dpsmith@apertussolutions.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Teddy Astie" <teddy.astie@vates.tech>,
"Frediano Ziglio" <frediano.ziglio@citrix.com>
Subject: Re: [PATCH v5 3/5] x86/efi: avoid a relocation in efi_arch_post_exit_boot()
Date: Tue, 30 Jun 2026 15:12:30 +0200 [thread overview]
Message-ID: <akPAvr7hF_6fjOh0@macbook.local> (raw)
In-Reply-To: <20260626123645.229375-4-frediano.ziglio@citrix.com>
On Fri, Jun 26, 2026 at 01:36:43PM +0100, Frediano Ziglio wrote:
> From: Roger Pau Monné <roger.pau@citrix.com>
>
> Instead of using the absolute __start_xen address, calculate it as an
> offset from the current instruction pointer. The relocation would be
> problematic if the generated PE binary had .init.text as a standalone
> section with just read and execute permissions."
There's a stray " at the end of the line I think.
Thanks, Roger.
next prev parent reply other threads:[~2026-06-30 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 12:36 [PATCH v5 0/5] Various patches to improve Secure Boot support Frediano Ziglio
2026-06-26 12:36 ` [PATCH v5 1/5] Align relevant sections to 4KB Frediano Ziglio
2026-06-26 12:36 ` [PATCH v5 2/5] x86/efi: discard multiboot and PVH support for PE binary Frediano Ziglio
2026-06-29 13:00 ` Jan Beulich
2026-06-26 12:36 ` [PATCH v5 3/5] x86/efi: avoid a relocation in efi_arch_post_exit_boot() Frediano Ziglio
2026-06-30 13:12 ` Roger Pau Monné [this message]
2026-06-26 12:36 ` [PATCH v5 4/5] x86: Split .init section to satisfy UEFI CA memory mitigation Frediano Ziglio
2026-06-26 12:36 ` [PATCH v5 5/5] x86/boot: Exclude not used string Frediano Ziglio
2026-06-29 13:59 ` Jan Beulich
2026-06-30 11:06 ` Andrew Cooper
2026-06-30 11:33 ` Jan Beulich
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=akPAvr7hF_6fjOh0@macbook.local \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dpsmith@apertussolutions.com \
--cc=freddy77@gmail.com \
--cc=frediano.ziglio@citrix.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=teddy.astie@vates.tech \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox