From: Hengqi Chen <hengqi.chen@gmail.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
hengqi.chen@gmail.com
Subject: [PATCH bpf-next v2 0/2] Support static initialization of BPF_MAP_TYPE_PROG_ARRAY
Date: Sun, 28 Nov 2021 22:16:31 +0800 [thread overview]
Message-ID: <20211128141633.502339-1-hengqi.chen@gmail.com> (raw)
Make libbpf support static initialization of BPF_MAP_TYPE_PROG_ARRAY
with a syntax similar to map-in-map initialization:
SEC("socket")
int tailcall_1(void *ctx)
{
return 0;
}
struct {
__uint(type, BPF_MAP_TYPE_PROG_ARRAY);
__uint(max_entries, 2);
__uint(key_size, sizeof(__u32));
__array(values, int (void *));
} prog_array_init SEC(".maps") = {
.values = {
[1] = (void *)&tailcall_1,
},
};
v1->v2:
- Add stricter checks on relos collect, some renamings (Andrii)
- Update selftest to check tailcall result (Andrii)
Hengqi Chen (2):
libbpf: Support static initialization of BPF_MAP_TYPE_PROG_ARRAY
selftests/bpf: Test BPF_MAP_TYPE_PROG_ARRAY static initialization
tools/lib/bpf/libbpf.c | 139 ++++++++++++++----
.../bpf/prog_tests/prog_array_init.c | 32 ++++
.../bpf/progs/test_prog_array_init.c | 39 +++++
3 files changed, 182 insertions(+), 28 deletions(-)
create mode 100644 tools/testing/selftests/bpf/prog_tests/prog_array_init.c
create mode 100644 tools/testing/selftests/bpf/progs/test_prog_array_init.c
--
2.30.2
next reply other threads:[~2021-11-28 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 14:16 Hengqi Chen [this message]
2021-11-28 14:16 ` [PATCH bpf-next v2 1/2] libbpf: Support static initialization of BPF_MAP_TYPE_PROG_ARRAY Hengqi Chen
2021-11-29 6:31 ` Andrii Nakryiko
2021-11-28 14:16 ` [PATCH bpf-next v2 2/2] selftests/bpf: Test BPF_MAP_TYPE_PROG_ARRAY static initialization Hengqi Chen
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=20211128141633.502339-1-hengqi.chen@gmail.com \
--to=hengqi.chen@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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