bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Chikunov <vt@altlinux.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, "Anton V. Boyarshinov" <boyarsh@altlinux.org>
Subject: Re: EFI boot fails when CONFIG_DEBUG_INFO_BTF=y on arm64
Date: Wed, 24 Feb 2021 18:43:40 +0300	[thread overview]
Message-ID: <20210224154340.mxjhr7odpu33vou7@altlinux.org> (raw)
In-Reply-To: <CAEf4BzZNS_BQhjRuT25YEa0ppU=4_v5kUqMxOaW_FqdXXDtVNg@mail.gmail.com>

Andrii,

On Mon, Feb 22, 2021 at 05:30:09PM -0800, Andrii Nakryiko wrote:
> 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).

Thanks for the reply! After some experiments and debugging today it's
turned out that problem is low default memory size for qemu. When
increased to `-m 512` it booted good. Thereby, now we can enable BTF for
aarch64 too.

Vitaly,

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

      reply	other threads:[~2021-02-24 16:09 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
2021-02-24 15:43   ` Vitaly Chikunov [this message]

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=20210224154340.mxjhr7odpu33vou7@altlinux.org \
    --to=vt@altlinux.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=boyarsh@altlinux.org \
    --cc=bpf@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;
as well as URLs for NNTP newsgroup(s).