From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Jan Beulich" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] x86: slightly simplify MB2/EFI "magic" check
Date: Mon, 12 Aug 2024 15:34:30 +0100 [thread overview]
Message-ID: <D3E0A9YVBOAD.LLLJMNX31BG6@cloud.com> (raw)
In-Reply-To: <f2186827-62e6-4b24-8a6c-0c2a9499c232@suse.com>
Hi,
On Thu Aug 8, 2024 at 9:49 AM BST, Jan Beulich wrote:
> A few dozen lines down from here we repeatedly use a pattern involving
> just a single (conditional) branch. Do so also when checking for the
> boot loader magic value.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> I further question the placement of the clearing of vga_text_buffer,
> just out of context: Shouldn't that be placed with the increments of
> efi_platform and skip_realmode? Or else is the terminology in comments
> ("on EFI platforms") wrong in one of the two places? In the end, if we
> are entered at __efi64_mb2_start but the magic doesn't match, we simply
> don't know what environment we're in. There may or may not be a VGA
> console at the default address, so we may as well (try to) write to it
> (just like we do when entered at start).
It's fair to assume we're in 64bits, and in that situation it's also fair to
assume the text console is long gone (pun intended). Seeing how this would be a
boot protocol bug, I think the most reasonable thing to do is to leave a poison
value in RAX and then hang (deadbeef..., badcafe..., take a pick). That would
point the poor sod debugging this to the right part of the code.
Though this is a largely theoretical issue that I can't see happening in
practice.
>
> --- a/xen/arch/x86/boot/head.S
> +++ b/xen/arch/x86/boot/head.S
> @@ -233,13 +233,11 @@ __efi64_mb2_start:
>
> /* Check for Multiboot2 bootloader. */
> cmp $MULTIBOOT2_BOOTLOADER_MAGIC,%eax
> - je .Lefi_multiboot2_proto
>
> /* Jump to .Lnot_multiboot after switching CPU to x86_32 mode. */
> lea .Lnot_multiboot(%rip), %r15
I don't think there's much benefit to this, but it would read more naturally if
lea was before cmp. Then cmp would be next to its (new) associated jne.
> - jmp x86_32_switch
> + jne x86_32_switch
>
> -.Lefi_multiboot2_proto:
> /* Zero EFI SystemTable, EFI ImageHandle addresses and cmdline. */
> xor %esi,%esi
> xor %edi,%edi
Cheers,
Alejandro
next prev parent reply other threads:[~2024-08-12 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 8:49 [PATCH] x86: slightly simplify MB2/EFI "magic" check Jan Beulich
2024-08-08 9:36 ` Frediano Ziglio
2024-08-08 9:54 ` Jan Beulich
2024-08-12 14:34 ` Alejandro Vallejo [this message]
2024-08-12 14:43 ` Jan Beulich
2024-08-12 17:35 ` Alejandro Vallejo
2024-08-12 21:40 ` Andrew Cooper
2024-08-13 7:02 ` 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=D3E0A9YVBOAD.LLLJMNX31BG6@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.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.