From: Tony Ambardar <tony.ambardar@gmail.com>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: dwarves@vger.kernel.org, bpf@vger.kernel.org,
Alan Maguire <alan.maguire@oracle.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH dwarves v2] dwarf_loader: Fix skipped encoding of function BTF on 32-bit systems
Date: Mon, 12 May 2025 01:41:36 -0700 [thread overview]
Message-ID: <aCG0QKuwuOpGrZgs@kodidev-ubuntu> (raw)
In-Reply-To: <D9RHP83CJA32.1LGMU4SC9QJ1K@bootlin.com>
On Fri, May 09, 2025 at 10:33:50AM +0200, Alexis Lothoré wrote:
> On Fri May 9, 2025 at 7:21 AM CEST, Tony Ambardar wrote:
> > Hi Alexis,
> >
> > On Thu, May 08, 2025 at 11:38:06AM +0200, Alexis Lothoré wrote:
> >> Hello,
>
> [...]
>
> > Nice! I notice bootlin has worked on several BPF testing contributions,
> > and was wondering if your build is some new standard buildroot/yocto
> > config tailored for BPF testing, and what archs it might support? Reason
> > for asking is I have a large stack of WIP patches for enabling use of
> > test_progs across 64/32-bit archs and cross-compilation, and I'm keen to
> > see other examples of configs, root images, etc. (especially for 32-bit)
> > At the moment I'm targeting 32-bit armhf support to make progress..
>
> No, that's really a custom, minimal setup that I am using, based on
> buildroot. My workflow is roughly the following:
> - use buildroot to download an arm64 toolchain and build a minimal rootfs.
> No specific defconfig used, it is a configuration from scratch, with
> additional tools for development and debugging
> - configure a kernel for arm64 testing:
> $ cat tools/testing/selftest/bpf/{config,config.vm,config.aarch64} >
> .config
> - use the toolchain downloaded by buildroot to build the kernel
> - build the selftests with the same toolchain (so I am cross-building those
> directly from my host, I am not really using vmtest)
> - run all of those in qemu, and run the selftests directly with test_progs
> in there
Understood, and thanks for the details. I basically do the same, with only a
couple of differences intended to ease adding armhf as a bpf-ci target
eventually:
- use the Ubuntu arm cross-toolchain to build on x86_64
- use mkrootfs tools from bpf-ci to make a Debian Bookworm rootfs
Take care,
Tony
>
> Alexis
>
> --
> Alexis Lothoré, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
next prev parent reply other threads:[~2025-05-12 8:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 8:33 [PATCH dwarves v1] dwarf_loader: Fix skipped encoding of function BTF on 32-bit systems Tony Ambardar
2025-04-10 12:20 ` Alan Maguire
2025-04-16 10:33 ` Tony Ambardar
2025-05-02 7:03 ` [PATCH dwarves v2] " Tony Ambardar
2025-05-08 9:38 ` Alexis Lothoré
2025-05-09 5:21 ` Tony Ambardar
2025-05-09 8:33 ` Alexis Lothoré
2025-05-12 8:41 ` Tony Ambardar [this message]
2025-05-08 13:24 ` Alan Maguire
2025-05-09 5:22 ` Tony Ambardar
2025-05-22 6:37 ` [PATCH dwarves v3] " Tony Ambardar
2025-06-24 16:14 ` Alan Maguire
2025-06-30 10:01 ` Alan Maguire
2025-06-30 13:51 ` Jiri Olsa
2025-06-30 17:32 ` Alan Maguire
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=aCG0QKuwuOpGrZgs@kodidev-ubuntu \
--to=tony.ambardar@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dwarves@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 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.