All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] x86: use EFI calling convention for efi_main on x86_64
Date: Thu, 31 May 2018 22:07:32 +0300	[thread overview]
Message-ID: <CAHp75Vd1J1oxCrsxkFFYCD=t=ovXcisgEn7WnNjhh0smC-8hpw@mail.gmail.com> (raw)
In-Reply-To: <097b82b4fb11b0ad047df04508358098c9164f73.1527791921.git.ivan.gorinov@intel.com>

On Thu, May 31, 2018 at 9:46 PM, Ivan Gorinov <ivan.gorinov@intel.com> wrote:
> UEFI specifies the calling convention used in Microsoft compilers;
> first arguments of a function are passed in (%rcx, %rdx, %r8, %r9).
>
> All other compilers use System V ABI by default, passing first integer
> arguments of a function in (%rdi, %rsi, %rdx, %rcx, %r8, %r9).
>
> These ABI also specify different sets of registers that must be preserved
> across function calls (callee-saved).
>
> GCC allows using the Microsoft calling convention by adding the ms_abi
> attribute to a function declaration.
>
> Current EFI implementation in U-Boot specifies EFIAPI for efi_main()
> in the test apps but uses default calling convention in lib/efi.
> The arguments of efi_main() are also passed as unused arguments to the
> _relocate() function.
>
> Save efi_main() arguments in the startup code on x86_64;
> use EFI calling convention for _relocate() on x86_64;
> remove unused _relocate() arguments;
> consistently use EFI calling convention for efi_main() everywhere.

Thanks, FWIW,

Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>

>
> Signed-off-by: Ivan Gorinov <ivan.gorinov@intel.com>
> ---
>  arch/x86/lib/crt0_x86_64_efi.S  | 21 ++++++++++-----------
>  arch/x86/lib/reloc_x86_64_efi.c |  3 +--
>  lib/efi/efi_app.c               |  3 ++-
>  lib/efi/efi_stub.c              |  3 ++-
>  4 files changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/lib/crt0_x86_64_efi.S b/arch/x86/lib/crt0_x86_64_efi.S
> index 989799f..3abb5e3 100644
> --- a/arch/x86/lib/crt0_x86_64_efi.S
> +++ b/arch/x86/lib/crt0_x86_64_efi.S
> @@ -3,7 +3,7 @@
>   * crt0-efi-x86_64.S - x86_64 EFI startup code.
>   * Copyright (C) 1999 Hewlett-Packard Co.
>   * Contributed by David Mosberger <davidm@hpl.hp.com>.
> - * Copyright (C) 2005 Intel Co.
> + * Copyright (C) 2005 Intel Corporation
>   * Contributed by Fenghua Yu <fenghua.yu@intel.com>.
>   *
>   * All rights reserved.
> @@ -14,26 +14,25 @@
>         .globl _start
>  _start:
>         subq $8, %rsp
> +
>         pushq %rcx
>         pushq %rdx
>
> -0:
> -       lea image_base(%rip), %rdi
> -       lea _DYNAMIC(%rip), %rsi
> +       lea image_base(%rip), %rcx
> +       lea _DYNAMIC(%rip), %rdx
>
> -       popq %rcx
> -       popq %rdx
> -       pushq %rcx
> -       pushq %rdx
>         call _relocate
>
> -       popq %rdi
> -       popq %rsi
> +       popq %rdx
> +       popq %rcx
> +
> +       testq %rax, %rax
> +       jnz _exit
>
>         call efi_main
> +_exit:
>         addq $8, %rsp
>
> -.exit:
>         ret
>
>         /*
> diff --git a/arch/x86/lib/reloc_x86_64_efi.c b/arch/x86/lib/reloc_x86_64_efi.c
> index 34c5b2e..59d6f8d 100644
> --- a/arch/x86/lib/reloc_x86_64_efi.c
> +++ b/arch/x86/lib/reloc_x86_64_efi.c
> @@ -14,8 +14,7 @@
>  #include <elf.h>
>  #include <asm/elf.h>
>
> -efi_status_t _relocate(long ldbase, Elf64_Dyn *dyn, efi_handle_t image,
> -                      struct efi_system_table *systab)
> +efi_status_t EFIAPI _relocate(long ldbase, Elf64_Dyn *dyn)
>  {
>         long relsz = 0, relent = 0;
>         Elf64_Rel *rel = 0;
> diff --git a/lib/efi/efi_app.c b/lib/efi/efi_app.c
> index c828093..3eb8eeb 100644
> --- a/lib/efi/efi_app.c
> +++ b/lib/efi/efi_app.c
> @@ -96,7 +96,8 @@ static void free_memory(struct efi_priv *priv)
>   * U-Boot. If it returns, EFI will continue. Another way to get back to EFI
>   * is via reset_cpu().
>   */
> -efi_status_t efi_main(efi_handle_t image, struct efi_system_table *sys_table)
> +efi_status_t EFIAPI efi_main(efi_handle_t image,
> +                            struct efi_system_table *sys_table)
>  {
>         struct efi_priv local_priv, *priv = &local_priv;
>         efi_status_t ret;
> diff --git a/lib/efi/efi_stub.c b/lib/efi/efi_stub.c
> index 3138739..399d16b 100644
> --- a/lib/efi/efi_stub.c
> +++ b/lib/efi/efi_stub.c
> @@ -268,7 +268,8 @@ static void add_entry_addr(struct efi_priv *priv, enum efi_entry_t type,
>   * This function is called by our EFI start-up code. It handles running
>   * U-Boot. If it returns, EFI will continue.
>   */
> -efi_status_t efi_main(efi_handle_t image, struct efi_system_table *sys_table)
> +efi_status_t EFIAPI efi_main(efi_handle_t image,
> +                            struct efi_system_table *sys_table)
>  {
>         struct efi_priv local_priv, *priv = &local_priv;
>         struct efi_boot_services *boot = sys_table->boottime;
> --
> 2.7.4
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot



-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2018-05-31 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 18:46 [U-Boot] [PATCH v3] x86: use EFI calling convention for efi_main on x86_64 Ivan Gorinov
2018-05-31 18:46 ` Ivan Gorinov
2018-05-31 19:07   ` Andy Shevchenko [this message]
2018-06-03 12:09   ` Alexander Graf
2018-06-12 12:25   ` Bin Meng

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='CAHp75Vd1J1oxCrsxkFFYCD=t=ovXcisgEn7WnNjhh0smC-8hpw@mail.gmail.com' \
    --to=andy.shevchenko@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.