Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Thomas Petazzoni via buildroot <buildroot@buildroot.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 3/3] support/testing: add bpftrace test
Date: Sat, 29 Aug 2026 18:52:08 +0200	[thread overview]
Message-ID: <ea3adbc598ea273edba25e595fad4969@free.fr> (raw)
In-Reply-To: <8733vxypoh.fsf@dell.be.48ers.dk>

Hi Peter, Thomas,

On 29/08/2026 16:19, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni via buildroot 
>>>>>> <buildroot@buildroot.org> writes:
> 
>  > This commit adds a simple bpftrace test that ensures that not only 
> it
>  > builds fine, but it also runs properly on a minimal test scenario.
> 
>  > +    config = f"""
>  > +        BR2_aarch64=y
>  > +        BR2_TOOLCHAIN_EXTERNAL=y
>  > +        BR2_TARGET_GENERIC_GETTY_PORT="ttyAMA0"
>  > +        BR2_LINUX_KERNEL=y
>  > +        BR2_LINUX_KERNEL_CUSTOM_VERSION=y
>  > +        BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.32"
> 
> Any specific reason to use such an old kernel? The qemu_aarch64_virt
> defconfig uses a 6.18 kernel. Is it to match the default ARM 15.2
> external toolchain? If so, that one is built against 6.6.44.
> 
> cat 
> output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/include/linux/version.h
> #define LINUX_VERSION_CODE 394796
> #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + ((c) > 255 ? 
> 255 : (c)))
> #define LINUX_VERSION_MAJOR 6
> #define LINUX_VERSION_PATCHLEVEL 6
> #define LINUX_VERSION_SUBLEVEL 44

I initially had the same question. Then, I assumed this new runtime test
has been simply copied from the existing test_bcc:
https://gitlab.com/buildroot.org/buildroot/-/blob/master/support/testing/tests/package/test_bcc.py
which was written with kernel 6.6.32, which was the latest LTS at that 
time.

Once the next 2026.08 release will be complete, I think we will do a 
cleanup
in runtime tests, to add a Aarch64 builtin kernel at the latest LTS. So 
all
those runtime tests will be updated.

> --
> Bye, Peter Korsgaard

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-29 16:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  9:55 [Buildroot] [PATCH 1/3] package/libbpf: update UAPI header installation work-around Thomas Petazzoni via buildroot
2026-08-27  9:55 ` [Buildroot] [PATCH 2/3] package/bpftrace: bump to version 0.26.1 to fix build with LLVM 22 Thomas Petazzoni via buildroot
2026-09-04 12:17   ` Thomas Perale via buildroot
2026-08-27  9:55 ` [Buildroot] [PATCH 3/3] support/testing: add bpftrace test Thomas Petazzoni via buildroot
2026-08-29 14:19   ` Peter Korsgaard
2026-08-29 16:52     ` Julien Olivain via buildroot [this message]
2026-08-29 17:49       ` Peter Korsgaard
2026-08-29 18:45       ` Thomas Petazzoni via buildroot
2026-08-29 19:24         ` Julien Olivain via buildroot
2026-09-04 12:19   ` Thomas Perale via buildroot
2026-08-28 10:58 ` [Buildroot] [PATCH 1/3] package/libbpf: update UAPI header installation work-around Julien Olivain via buildroot
2026-09-04 12:17 ` Thomas Perale via buildroot

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=ea3adbc598ea273edba25e595fad4969@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=peter@korsgaard.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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