From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] x86/boot: Untangle the trampoline copying/entry logic
Date: Wed, 19 Mar 2025 10:05:33 +0100 [thread overview]
Message-ID: <Z9qI3cnE3BcuqAPE@macbook.local> (raw)
In-Reply-To: <20250318201033.60634-1-andrew.cooper3@citrix.com>
On Tue, Mar 18, 2025 at 08:10:33PM +0000, Andrew Cooper wrote:
> The LRET is detached from the PUSHes which set it up, and this is about to get
> worse with the changes to trampoline relocation. For the sake of one variable
> read, the complexity is not worth it.
>
> Reorder the logic to copy the trampoline into place, then switch stack and
> enter the trampoline.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
> ---
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Roger Pau Monné <roger.pau@citrix.com>
>
> Roger: I'd like this to be a prerequisite to your "[PATCH 4/7] x86/boot: apply
> trampoline relocations at destination position" to avoid the movement of
> reloc_trampoline32() making things worse.
I think you could commit this now-ish, and I can rebase on top?
Thanks, Roger.
next prev parent reply other threads:[~2025-03-19 9:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 17:35 [PATCH 0/7] x86: generate xen.efi image with no write-execute sections Roger Pau Monne
2025-03-18 17:35 ` [PATCH 1/7] x86/boot: clarify comment about trampoline_setup usage Roger Pau Monne
2025-03-18 17:45 ` Andrew Cooper
2025-03-19 8:46 ` Roger Pau Monné
2025-03-19 12:22 ` Andrew Cooper
2025-03-18 17:35 ` [PATCH 2/7] x86/mkelf32: account for offset when detecting note segment placement Roger Pau Monne
2025-03-18 17:45 ` Andrew Cooper
2025-03-19 10:07 ` Jan Beulich
2025-03-19 14:16 ` Roger Pau Monné
2025-03-19 14:33 ` Jan Beulich
2025-03-18 17:35 ` [PATCH 3/7] xen: remove -N from the linker command line Roger Pau Monne
2025-03-18 17:53 ` Andrew Cooper
2025-03-19 10:20 ` Jan Beulich
2025-03-21 16:28 ` Oleksii Kurochko
2025-03-18 17:35 ` [PATCH 4/7] x86/boot: apply trampoline relocations at destination position Roger Pau Monne
2025-03-18 19:05 ` Frediano Ziglio
2025-03-18 19:17 ` Andrew Cooper
2025-03-19 12:00 ` Frediano Ziglio
2025-03-18 20:10 ` [PATCH] x86/boot: Untangle the trampoline copying/entry logic Andrew Cooper
2025-03-19 9:05 ` Roger Pau Monné [this message]
2025-03-20 13:59 ` Andrew Cooper
2025-03-18 20:14 ` [PATCH 4/7] x86/boot: apply trampoline relocations at destination position Andrew Cooper
2025-03-18 17:35 ` [PATCH 5/7] x86/mkreloc: remove warning about relocations to RO section Roger Pau Monne
2025-03-18 18:14 ` Andrew Cooper
2025-03-19 10:32 ` Jan Beulich
2025-03-19 10:46 ` Jan Beulich
2025-03-19 10:53 ` Jan Beulich
2025-03-20 8:14 ` Roger Pau Monné
2025-03-20 8:34 ` Jan Beulich
2025-03-20 9:53 ` Jan Beulich
2025-03-20 10:18 ` Jan Beulich
2025-03-20 11:00 ` Andrew Cooper
2025-03-20 11:11 ` Jan Beulich
2025-03-18 17:35 ` [PATCH 6/7] x86/efi: do not merge all .init sections Roger Pau Monne
2025-03-18 18:08 ` Andrew Cooper
2025-03-19 10:39 ` Jan Beulich
2025-03-18 17:35 ` [PATCH 7/7] xen/build: warn about RWX load segments Roger Pau Monne
2025-03-18 18:07 ` 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=Z9qI3cnE3BcuqAPE@macbook.local \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@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.