From: Eduard Zingerman <eddyz87@gmail.com>
To: Ihor Solodrai <ihor.solodrai@linux.dev>,
Alan Maguire <alan.maguire@oracle.com>,
andrii@kernel.org, dwarves@vger.kernel.org, acme@kernel.org
Cc: bpf@vger.kernel.org, ast@kernel.org, tj@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH dwarves v1 0/3] btf_encoder: support for BPF magic kernel functions
Date: Tue, 04 Nov 2025 14:33:32 -0800 [thread overview]
Message-ID: <0db4e51eed95f9d4616ff5936d335ae71ac2a016.camel@gmail.com> (raw)
In-Reply-To: <ba1650aa-fafd-49a8-bea4-bdddee7c38c9@linux.dev>
On Tue, 2025-11-04 at 14:25 -0800, Ihor Solodrai wrote:
> On 11/4/25 12:59 PM, Alan Maguire wrote:
> > On 29/10/2025 19:02, Ihor Solodrai wrote:
> > > This series implements BTF encoding of BPF kernel functions marked
> > > with KF_MAGIC_ARGS flag in pahole.
> > >
> > > The kfunc flag indicates that the arguments of a kfunc with __magic
> > > suffix are implicitly set by the verifier, and so pahole must emit two
> > > functions to BTF:
> > > * kfunc_impl() with the arguments matching kernel declaration
> > > * kfunc() with __magic arguments omitted
> > >
> > > For more details see relevant patch series for BPF:
> > > "bpf: magic kernel functions"
> > >
> > > This series is built upon KF_IMPLICIT_PROG_AUX_ARG support [1],
> > > although the approach changed signifcantly to call it a v2.
> > >
> > > [1] https://lore.kernel.org/dwarves/20250924211512.1287298-1-ihor.solodrai@linux.dev/
> > >
> > > Ihor Solodrai (3):
> > > btf_encoder: refactor btf_encoder__add_func_proto
> > > btf_encoder: factor out btf_encoder__add_bpf_kfunc()
> > > btf_encoder: support kfuncs with KF_MAGIC_ARGS flag
> > >
> > > btf_encoder.c | 292 ++++++++++++++++++++++++++++++++++++++------------
> > > 1 file changed, 222 insertions(+), 70 deletions(-)
> > >
> >
> > seems like we could potentially pull in patches 1 and 2 as cleanups
> > prior to handling the KF_MAGIC/IMPLICIT change; would that be worthwhile?
> >
>
> Hi Alan.
>
> Feel free to merge in the refactoring patches if you think they are
> useful. No objections.
Hi Alan, Ihor,
If you thinking about merging patch #1, please consider my comment:
> > +static int32_t btf_encoder__add_func_proto_for_state(struct btf_encoder *encoder, struct btf_encoder_func_state *state)
> You can get rid of the `encoder` parameter here.
> See https://github.com/acmel/dwarves/commit/080d1f27ae71e30c269a1e26e85bb86c3683f195 .
I sound a bit like a broken record, sorry.
[...]
next prev parent reply other threads:[~2025-11-04 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 19:02 [PATCH dwarves v1 0/3] btf_encoder: support for BPF magic kernel functions Ihor Solodrai
2025-10-29 19:02 ` [PATCH dwarves v1 1/3] btf_encoder: refactor btf_encoder__add_func_proto Ihor Solodrai
2025-10-30 0:34 ` Eduard Zingerman
2025-10-29 19:02 ` [PATCH dwarves v1 2/3] btf_encoder: factor out btf_encoder__add_bpf_kfunc() Ihor Solodrai
2025-10-29 19:02 ` [PATCH dwarves v1 3/3] btf_encoder: support kfuncs with KF_MAGIC_ARGS flag Ihor Solodrai
2025-11-04 20:59 ` [PATCH dwarves v1 0/3] btf_encoder: support for BPF magic kernel functions Alan Maguire
2025-11-04 22:25 ` Ihor Solodrai
2025-11-04 22:33 ` Eduard Zingerman [this message]
2025-11-04 22:37 ` Ihor Solodrai
2025-11-14 18:33 ` 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=0db4e51eed95f9d4616ff5936d335ae71ac2a016.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=tj@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).