From: Victor Erminpour <victor.erminpour@oracle.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] efi/libstub/arm64: Enable __efistub_global define in .data section
Date: Fri, 10 Apr 2020 15:12:13 -0700 [thread overview]
Message-ID: <aee6c7cc-24c7-2822-47d5-1e05413a8024@oracle.com> (raw)
In-Reply-To: <CAMj1kXGgYYx=9rq-Ficw3vS6FX_0nb-hRStXijh7H4zdD=+Gaw@mail.gmail.com>
On 4/10/20 1:09 AM, Ard Biesheuvel wrote:
> On Thu, 9 Apr 2020 at 23:44, Victor Erminpour
> <victor.erminpour@oracle.com> wrote:
>>
>> Enable the __efistub_global define to place variables in the
>> .data section for both CONFIG_ARM and CONFIG_ARM64.
>>
>> This places the EFIstub sys_table variable and other EFIstub
>> static variables in the .data section for both CONFIG_ARM and
>> CONFIG_ARM64.
>>
>
> What does that achieve?
Hi Ard,
Without placing these global variables in .data, I get the
following errors when booting an ARM64 EFI system:
EFI stub: ERROR: Exit boot services failed.
EFI stub: ERROR: Failed to update FDT and exit boot services
I know that the ARM64 linker script is supposed to put the
.init.bss into the .init.data section, but I don't think this
is happening for all systems.
Having it explicitly enabled for CONFIG_ARM64 worked for me.
Regards,
--Victor
>
>> Signed-off-by: Victor Erminpour <victor.erminpour@oracle.com>
>> ---
>> drivers/firmware/efi/libstub/efistub.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/firmware/efi/libstub/efistub.h b/drivers/firmware/efi/libstub/efistub.h
>> index c244b16..59932d6 100644
>> --- a/drivers/firmware/efi/libstub/efistub.h
>> +++ b/drivers/firmware/efi/libstub/efistub.h
>> @@ -25,7 +25,7 @@
>> #define EFI_ALLOC_ALIGN EFI_PAGE_SIZE
>> #endif
>>
>> -#ifdef CONFIG_ARM
>> +#if defined(CONFIG_ARM) || defined(CONFIG_ARM64)
>> #define __efistub_global __section(.data)
>> #else
>> #define __efistub_global
--
Victor Hugo Erminpour
Principal Member of Technical Staff
Oracle America
next prev parent reply other threads:[~2020-04-10 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 21:44 Victor Erminpour
2020-04-10 8:09 ` Ard Biesheuvel
2020-04-10 22:12 ` Victor Erminpour [this message]
2020-04-11 6:39 ` Ard Biesheuvel
2020-04-13 13:46 ` Arvind Sankar
2020-04-13 22:56 ` Victor Erminpour
2020-04-14 6:46 ` Ard Biesheuvel
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=aee6c7cc-24c7-2822-47d5-1e05413a8024@oracle.com \
--to=victor.erminpour@oracle.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®