All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: EFI boot fails when CONFIG_DEBUG_INFO_BTF=y on arm64
Date: Mon, 22 Feb 2021 17:30:09 -0800	[thread overview]
Message-ID: <CAEf4BzZNS_BQhjRuT25YEa0ppU=4_v5kUqMxOaW_FqdXXDtVNg@mail.gmail.com> (raw)
In-Reply-To: <20210211233956.em5k4vtefyfp4tiv@altlinux.org>

On Thu, Feb 11, 2021 at 3:44 PM Vitaly Chikunov <vt@altlinux.org> wrote:
>
> Hi,
>
> We have boot test using OVMF/AAVMF EFI firmware on aarch64 in qemu. When
> we try to build kernel with `CONFIG_DEBUG_INFO_BTF=y' (pahole v1.20)
> previously successful EFI boot test fails with:
>
>   EFI stub: ERROR: Failed to relocate kernel
>   EFI stub: ERROR: Failed to relocate kernel
>
> Without EFI it boots normally. On other our architectures (such as
> arm32, i586, powerpc, x86_64) it boots normally too (all without EFI
> boot, but x86_64 is also successfully tested with OVMF EFI boot).

So this seems like an arm64-specific issue? Is it possible to get any
help from someone familiar with arm64 specifics to find out what
exactly causes this problem? We use `pahole -J` to "implant" .BTF into
vmlinux.o, but later rely on vmlinux loader scripts to have a loadable
.BTF section. The problem might happen somewhere along those steps. I
don't think I can be of much help here without a bit more information
(and seems like no one else on this list came up with any suggestions
as well).

>
> This is tested on 5.4.97, but I can try 5.10.15 if needed.
>
> Thanks,
>

  reply	other threads:[~2021-02-23  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 23:39 EFI boot fails when CONFIG_DEBUG_INFO_BTF=y on arm64 Vitaly Chikunov
2021-02-23  1:30 ` Andrii Nakryiko [this message]
2021-02-24 15:43   ` Vitaly Chikunov

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='CAEf4BzZNS_BQhjRuT25YEa0ppU=4_v5kUqMxOaW_FqdXXDtVNg@mail.gmail.com' \
    --to=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=vt@altlinux.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.