From: Martin KaFai Lau <martin.lau@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: daniel@iogearbox.net, andrii@kernel.org, martin.lau@kernel.org,
void@manifault.com, davemarchevsky@meta.com, tj@kernel.org,
memxor@gmail.com, netdev@vger.kernel.org, bpf@vger.kernel.org,
kernel-team@fb.com, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH bpf-next 0/2] bpf: Add detection of kfuncs.
Date: Wed, 15 Mar 2023 17:33:45 -0700 [thread overview]
Message-ID: <e976396c-0eaa-b7f6-847c-597e68f78815@linux.dev> (raw)
In-Reply-To: <20230315223607.50803-1-alexei.starovoitov@gmail.com>
On 3/15/23 3:36 PM, Alexei Starovoitov wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Allow BPF programs detect at load time whether particular kfunc exists.
Reviewed-by: Martin KaFai Lau <martin.lau@kernel.org>
next prev parent reply other threads:[~2023-03-16 0:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 22:36 [PATCH bpf-next 0/2] bpf: Add detection of kfuncs Alexei Starovoitov
2023-03-15 22:36 ` [PATCH bpf-next 1/2] bpf: Allow ld_imm64 instruction to point to kfunc Alexei Starovoitov
2023-03-16 14:14 ` Eduard Zingerman
2023-03-16 16:45 ` Alexei Starovoitov
2023-03-16 20:34 ` Andrii Nakryiko
2023-03-16 22:25 ` Alexei Starovoitov
2023-03-16 23:06 ` Andrii Nakryiko
2023-03-17 1:39 ` Alexei Starovoitov
2023-03-17 16:28 ` Andrii Nakryiko
2023-03-15 22:36 ` [PATCH bpf-next 2/2] selftests/bpf: Add test for bpf_kfunc_exists() Alexei Starovoitov
2023-03-16 20:34 ` Andrii Nakryiko
2023-03-16 22:35 ` Alexei Starovoitov
2023-03-16 23:23 ` Andrii Nakryiko
2023-03-16 0:33 ` Martin KaFai Lau [this message]
2023-03-16 5:34 ` [PATCH bpf-next 0/2] bpf: Add detection of kfuncs John Fastabend
2023-03-16 10:31 ` Toke Høiland-Jørgensen
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=e976396c-0eaa-b7f6-847c-597e68f78815@linux.dev \
--to=martin.lau@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=davemarchevsky@meta.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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;
as well as URLs for NNTP newsgroup(s).