From: Matt Fleming <matt@codeblueprint.co.uk>
To: Jiri Slaby <jslaby@suse.cz>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 3/5] x86_64: boot, extract efi_pe_entry from startup_64
Date: Mon, 5 Jun 2017 15:20:26 +0100 [thread overview]
Message-ID: <20170605142026.GD3339@codeblueprint.co.uk> (raw)
In-Reply-To: <20170531081243.5709-3-jslaby@suse.cz>
On Wed, 31 May, at 10:12:41AM, Jiri Slaby wrote:
> efi_pe_entry body is somehow squashed into startup_64. In the old days,
> we forced startup_64 to start at offset 0x200 and efi_pe_entry to start
> at 0x210. But this requirement was removed in 99f857db8857 ("x86, build:
> Dynamically find entry points in compressed startup code") long time
> ago.
>
> The way it is now makes the code less readable and illogical. And given
> we can now safely extract the inlined efi_pe_entry body from
> startup_64 into a separate function, we do so.
>
> We also annotate the function appropriatelly by ENTRY+ENDPROC.
>
> ABI offsets are preserved:
> 0000000000000000 T startup_32
> 0000000000000200 T startup_64
> 0000000000000390 T efi64_stub_entry
>
> On the top-level, it looked like:
> .org 0x200
> ENTRY(startup_64)
> #ifdef CONFIG_EFI_STUB ; start of inlined
> jmp preferred_addr
> GLOBAL(efi_pe_entry)
> ... ; a lot of assembly (efi_pe_entry)
> leaq preferred_addr(%rax), %rax
> jmp *%rax
> preferred_addr:
> #endif ; end of inlined
> ... ; a lot of assembly (startup_64)
> ENDPROC(startup_64)
>
> And it is converted into:
> .org 0x200
> ENTRY(startup_64)
> ... ; a lot of assembly (startup_64)
> ENDPROC(startup_64)
>
> #ifdef CONFIG_EFI_STUB
> ENTRY(efi_pe_entry)
> ... ; a lot of assembly (efi_pe_entry)
> leaq startup_64(%rax), %rax
> jmp *%rax
> ENDPROC(efi_pe_entry)
> #endif
>
> Signed-off-by: Jiri Slaby <jslaby@suse.cz>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: <x86@kernel.org>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Matt Fleming <matt@codeblueprint.co.uk>
> ---
> arch/x86/boot/compressed/head_64.S | 112 ++++++++++++++++++-------------------
> 1 file changed, 53 insertions(+), 59 deletions(-)
Reviewed-by: Matt Fleming <matt@codeblueprint.co.uk>
next prev parent reply other threads:[~2017-06-05 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 8:12 [PATCH 1/5] x86: boot/copy, remove unused functions Jiri Slaby
2017-05-31 8:12 ` [PATCH 2/5] x86_32: boot, extract efi_pe_entry from startup_32 Jiri Slaby
2017-06-05 14:20 ` Matt Fleming
2017-05-31 8:12 ` [PATCH 3/5] x86_64: boot, extract efi_pe_entry from startup_64 Jiri Slaby
2017-06-05 14:20 ` Matt Fleming [this message]
2017-05-31 8:12 ` [PATCH 4/5] x86: math-emu, add ENDPROC to functions Jiri Slaby
2017-05-31 8:12 ` [PATCH 5/5] x86: entry, use ENTRY instead of ALIGN+GLOBAL for stub32_clone Jiri Slaby
2017-06-05 9:14 ` [tip:x86/boot] x86/boot: Remove unused copy_*_gs() functions tip-bot for Jiri Slaby
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=20170605142026.GD3339@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=dwmw2@infradead.org \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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