From: Lorenz Bauer <lorenz.bauer@isovalent.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-input@vger.kernel.org, coreteam@netfilter.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, fsverity@lists.linux.dev,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
cgroups@vger.kernel.org, alexei.starovoitov@gmail.com,
olsajiri@gmail.com, quentin@isovalent.com,
alan.maguire@oracle.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section
Date: Mon, 8 Jan 2024 10:15:45 +0100 [thread overview]
Message-ID: <CAN+4W8gPeQ2OjoYLKXsNPyhSVTB+vcSaS3Xzw=-M9Rf5MXfKPg@mail.gmail.com> (raw)
In-Reply-To: <cover.1704565248.git.dxu@dxuuu.xyz>
On Sat, Jan 6, 2024 at 7:25 PM Daniel Xu <dxu@dxuuu.xyz> wrote:
>
> === Description ===
>
> This is a bpf-treewide change that annotates all kfuncs as such inside
> .BTF_ids. This annotation eventually allows us to automatically generate
> kfunc prototypes from bpftool.
>
> We store this metadata inside a yet-unused flags field inside struct
> btf_id_set8 (thanks Kumar!). pahole will be taught where to look.
This is great, thanks for tackling this. With yout patches we can
figure out the full set of kfuncs. Is there a way to extend it so that
we can tell which program context a kfunc can be called from?
WARNING: multiple messages have this Message-ID (diff)
From: Lorenz Bauer <lorenz.bauer@isovalent.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-input@vger.kernel.org, coreteam@netfilter.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, fsverity@lists.linux.dev,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
cgroups@vger.kernel.org, alexei.starovoitov@gmail.com,
olsajiri@gmail.com, quentin@isovalent.com,
alan.maguire@oracle.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section
Date: Mon, 8 Jan 2024 10:15:45 +0100 [thread overview]
Message-ID: <CAN+4W8gPeQ2OjoYLKXsNPyhSVTB+vcSaS3Xzw=-M9Rf5MXfKPg@mail.gmail.com> (raw)
In-Reply-To: <cover.1704565248.git.dxu@dxuuu.xyz>
On Sat, Jan 6, 2024 at 7:25 PM Daniel Xu <dxu@dxuuu.xyz> wrote:
>
> === Description ===
>
> This is a bpf-treewide change that annotates all kfuncs as such inside
> .BTF_ids. This annotation eventually allows us to automatically generate
> kfunc prototypes from bpftool.
>
> We store this metadata inside a yet-unused flags field inside struct
> btf_id_set8 (thanks Kumar!). pahole will be taught where to look.
This is great, thanks for tackling this. With yout patches we can
figure out the full set of kfuncs. Is there a way to extend it so that
we can tell which program context a kfunc can be called from?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-08 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 18:24 [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section Daniel Xu
2024-01-06 18:24 ` Daniel Xu
2024-01-06 18:24 ` [PATCH bpf-next v3 1/3] bpf: btf: Support flags for BTF_SET8 sets Daniel Xu
2024-01-06 18:24 ` [PATCH bpf-next v3 2/3] bpf: btf: Add BTF_KFUNCS_START/END macro pair Daniel Xu
2024-01-08 9:14 ` Lorenz Bauer
2024-01-08 17:59 ` Daniel Xu
2024-01-11 1:27 ` Daniel Xu
2024-01-06 18:24 ` [PATCH bpf-next v3 3/3] bpf: treewide: Annotate BPF kfuncs in BTF Daniel Xu
2024-01-08 9:15 ` Lorenz Bauer [this message]
2024-01-08 9:15 ` [PATCH bpf-next v3 0/3] Annotate kfuncs in .BTF_ids section Lorenz Bauer
2024-01-08 17:52 ` Daniel Xu
2024-01-08 17:52 ` Daniel Xu
2024-01-12 16:20 ` Jiri Olsa
2024-01-12 16:20 ` Jiri Olsa
2024-01-12 20:03 ` Daniel Xu
2024-01-12 20:03 ` Daniel Xu
2024-01-13 13:57 ` Jiri Olsa
2024-01-13 13:57 ` Jiri Olsa
2024-01-13 16:17 ` Daniel Xu
2024-01-13 16:17 ` Daniel Xu
2024-01-13 19:49 ` Jiri Olsa
2024-01-13 19:49 ` Jiri Olsa
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='CAN+4W8gPeQ2OjoYLKXsNPyhSVTB+vcSaS3Xzw=-M9Rf5MXfKPg@mail.gmail.com' \
--to=lorenz.bauer@isovalent.com \
--cc=alan.maguire@oracle.com \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=coreteam@netfilter.org \
--cc=dxu@dxuuu.xyz \
--cc=fsverity@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=quentin@isovalent.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 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.