public inbox for dwarves@vger.kernel.org
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: dwarves@vger.kernel.org, alan.maguire@oracle.com, acme@kernel.org
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
	eddyz87@gmail.com, tj@kernel.org, kernel-team@meta.com
Subject: [PATCH dwarves v1 0/2] btf_encoder: KF_IMPLICIT_PROG_AUX_ARG support
Date: Wed, 24 Sep 2025 14:15:10 -0700	[thread overview]
Message-ID: <20250924211512.1287298-1-ihor.solodrai@linux.dev> (raw)

This series implements KF_IMPLICIT_PROG_AUX_ARG kfunc flag in pahole's
BTF encoding.

The kfunc flag indicates that the last argument of a BPF kfunc is a
pointer to struct bpf_prog_aux implicitly set by the verifier.

BTF function prototype of such a function must omit its last parameter
(expected to be of `struct bpf_prog_aux *` type), despite it being
present in the kernel declaration of the kfunc.

See also a the patch series for BPF:
"bpf: implicit bpf_prog_aux argument for kfuncs"

Ihor Solodrai (2):
  btf_encoder: refactor btf_encoder__add_func_proto
  btf_encoder: implement KF_IMPLICIT_PROG_AUX_ARG kfunc flag handling

 btf_encoder.c | 172 ++++++++++++++++++++++++++++++++++----------------
 1 file changed, 116 insertions(+), 56 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-09-24 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 21:15 Ihor Solodrai [this message]
2025-09-24 21:15 ` [PATCH dwarves v1 1/2] btf_encoder: refactor btf_encoder__add_func_proto Ihor Solodrai
2025-09-24 21:15 ` [PATCH dwarves v1 2/2] btf_encoder: implement KF_IMPLICIT_PROG_AUX_ARG kfunc flag handling Ihor Solodrai
2025-09-25  1:22   ` Eduard Zingerman
2025-09-25  3:59     ` Ihor Solodrai
2025-09-25 13:28       ` Eduard Zingerman
2025-09-25 17:15         ` Andrii Nakryiko

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=20250924211512.1287298-1-ihor.solodrai@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --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=eddyz87@gmail.com \
    --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