Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: romain.naour@smile.fr,
	Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 3/3] support/testing: add bpftrace test
Date: Sat, 29 Aug 2026 21:24:23 +0200	[thread overview]
Message-ID: <8aab4881ec10eb0524327ac9e9467fd7@free.fr> (raw)
In-Reply-To: <apMogNfb_5pg-OmH@windsurf>

Hi Thomas, All,

On 29/08/2026 20:45, Thomas Petazzoni wrote:
> On Sat, Aug 29, 2026 at 06:52:08PM +0200, Julien Olivain wrote:
> 
>> 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.
> 
> Absolutely correct. And of course, I see no problem in migrating all
> these tests to 6.18.
> 
>> 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.
> 
> I vaguely remember that one intern from Romain Naour was working on
> this, I even vaguely remember seeing patches implementing this, no?

If I try to summarize the state of this activity:

I merged a series a while back, updating many kernels
in runtime tests:
https://patchwork.ozlabs.org/project/buildroot/list/?series=500282&state=*

Then, there is an initiative to build the runtime test pre-built
Kernels from the Gitlab CI:
https://patchwork.buildroot.org/project/buildroot/list/?series=210
Ideally we would like to add new kernels (aarch64 for ex).

Then, there is ongoing work to switch most tests on the new relevant
pre-built kernels. I think the most advance ongoing work is at:
https://gitlab.com/kubu93/buildroot/-/commits/prebuilt-aarch64-kernel-v7

> Thomas
> --
> Thomas Petazzoni, co-owner and CEO, Bootlin
> Embedded Linux and Kernel engineering and training
> https://bootlin.com

Best regards,

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

  reply	other threads:[~2026-08-29 19:24 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
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 [this message]
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=8aab4881ec10eb0524327ac9e9467fd7@free.fr \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=romain.naour@smile.fr \
    --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