From: Eduard Zingerman <eddyz87@gmail.com>
To: Mykola Lysenko <nickolay.lysenko@gmail.com>, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, memxor@gmail.com
Subject: Re: [RFC PATCH bpf-next v5 6/8] selftests/bpf: extract BPF skeleton generation into a helper script
Date: Wed, 05 Aug 2026 15:39:04 -0700 [thread overview]
Message-ID: <25cea44482f4e8ca1d59116dff5b2b9b5948271c.camel@gmail.com> (raw)
In-Reply-To: <20260804170156.1709916-7-nickolay.lysenko@gmail.com>
On Tue, 2026-08-04 at 10:01 -0700, Mykola Lysenko wrote:
> The four skeleton generation recipes (regular, light, signed light and
> linked) are near-identical five-step pipelines - link via "bpftool gen
> object" three times, compare the second and third results as a
> regression test for bpftool's determinism, generate the skeleton (and
> possibly subskeleton), remove intermediates - duplicated with small
> variations inside DEFINE_TEST_RUNNER_RULES, where every line pays the
> double-expansion escaping tax.
>
> Move the pipeline into gen_bpf_skel.sh; the differences between the
> four variants become the --lskel, --sign and --subskel flags. Signing
> takes the key and certificate from $PRIVATE_KEY and $VERIFICATION_CERT
> in the environment, like the bpftool binary comes from $BPFTOOL. The
> distinct linked/llinked intermediate infixes are kept but derived
> inside the script: tests listed in LSKELS_EXTRA generate both a
> .skel.h and a .lskel.h from the same .bpf.o, and distinct intermediate
> names are what keeps parallel builds from racing. Build-log messages
> stay in the recipes with the usual $(call msg,...) helpers; behavior
> is unchanged.
>
> Suggested-by: Eduard Zingerman <eddyz87@gmail.com>
> Assisted-by: Claude:claude-fable-5 shellcheck
> Signed-off-by: Mykola Lysenko <nickolay.lysenko@gmail.com>
> ---
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
I need to print this out and hang it at my desk.
┌────────────┬─────────────────┬───────────────────────────┬─────┐
│ expression │ x unset │ x="" │ x=v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x-D} │ D │ `` (empty) │ v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x:-D} │ D │ D │ v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x+A} │ `` │ A │ A │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x:+A} │ `` │ `` │ A │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x=D} │ D (and assigns) │ `` (no assign — x is set) │ v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x:=D} │ D (and assigns) │ D (and assigns) │ v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x?msg} │ abort │ `` │ v │
├────────────┼─────────────────┼───────────────────────────┼─────┤
│ ${x:?msg} │ abort │ abort │ v │
└────────────┴─────────────────┴───────────────────────────┴─────┘
...
next prev parent reply other threads:[~2026-08-05 22:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 17:01 [RFC PATCH bpf-next v5 0/8] selftests/bpf: restructure the Makefile as a layered build Mykola Lysenko
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 1/8] selftests/bpf: keep headers off the generic link command line Mykola Lysenko
2026-08-05 21:21 ` Eduard Zingerman
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 2/8] selftests/bpf: drop stale and no-op lines Mykola Lysenko
2026-08-05 21:28 ` Eduard Zingerman
2026-08-06 4:43 ` Mykola Lysenko
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 3/8] selftests/bpf: factor the permissive-mode skip suffix into a helper Mykola Lysenko
2026-08-04 17:21 ` sashiko-bot
2026-08-05 0:13 ` Mykola Lysenko
2026-08-05 21:33 ` Eduard Zingerman
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 4/8] selftests/bpf: generate the signing key and certificate once Mykola Lysenko
2026-08-05 22:03 ` Eduard Zingerman
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 5/8] selftests/bpf: generate verifier/tests.h in a regular recipe Mykola Lysenko
2026-08-05 22:11 ` Eduard Zingerman
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 6/8] selftests/bpf: extract BPF skeleton generation into a helper script Mykola Lysenko
2026-08-04 17:59 ` sashiko-bot
2026-08-05 1:40 ` Mykola Lysenko
2026-08-05 22:39 ` Eduard Zingerman [this message]
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 7/8] selftests/bpf: move shared build definitions into Makefile.buildvars Mykola Lysenko
2026-08-05 23:34 ` Eduard Zingerman
2026-08-06 4:51 ` Mykola Lysenko
2026-08-04 17:01 ` [RFC PATCH bpf-next v5 8/8] selftests/bpf: build each test runner instance in its own sub-make Mykola Lysenko
2026-08-06 8:02 ` Eduard Zingerman
2026-08-06 18:30 ` Eduard Zingerman
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=25cea44482f4e8ca1d59116dff5b2b9b5948271c.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jolsa@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=nickolay.lysenko@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.