From: Lorenz Bauer <lmb@cloudflare.com>
To: ast@kernel.org, yhs@fb.com, daniel@iogearbox.net, kafai@fb.com,
andriin@fb.com
Cc: bpf@vger.kernel.org, kernel-team@cloudflare.com,
Lorenz Bauer <lmb@cloudflare.com>
Subject: [PATCH bpf-next v2 03/11] btf: Add BTF_ID_LIST_SINGLE macro
Date: Wed, 9 Sep 2020 18:11:47 +0100 [thread overview]
Message-ID: <20200909171155.256601-4-lmb@cloudflare.com> (raw)
In-Reply-To: <20200909171155.256601-1-lmb@cloudflare.com>
Add a convenience macro that allows defining a BTF ID list with
a single item. This lets us cut down on repetitive macros.
Signed-off-by: Lorenz Bauer <lmb@cloudflare.com>
Suggested-by: Andrii Nakryiko <andriin@fb.com>
---
include/linux/btf_ids.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/linux/btf_ids.h b/include/linux/btf_ids.h
index 210b086188a3..d6a959572175 100644
--- a/include/linux/btf_ids.h
+++ b/include/linux/btf_ids.h
@@ -76,6 +76,13 @@ extern u32 name[];
#define BTF_ID_LIST_GLOBAL(name) \
__BTF_ID_LIST(name, globl)
+/* The BTF_ID_LIST_SINGLE macro defines a BTF_ID_LIST with
+ * a single entry.
+ */
+#define BTF_ID_LIST_SINGLE(name, prefix, typename) \
+ BTF_ID_LIST(name) \
+ BTF_ID(prefix, typename)
+
/*
* The BTF_ID_UNUSED macro defines 4 zero bytes.
* It's used when we want to define 'unused' entry
--
2.25.1
next prev parent reply other threads:[~2020-09-09 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 17:11 [PATCH bpf-next v2 00/11] Make check_func_arg type checks table driven Lorenz Bauer
2020-09-09 17:11 ` [PATCH bpf-next v2 01/11] btf: make btf_set_contains take a const pointer Lorenz Bauer
2020-09-09 17:11 ` [PATCH bpf-next v2 02/11] bpf: check scalar or invalid register in check_helper_mem_access Lorenz Bauer
2020-09-09 17:11 ` Lorenz Bauer [this message]
2020-09-09 18:09 ` [PATCH bpf-next v2 03/11] btf: Add BTF_ID_LIST_SINGLE macro Martin KaFai Lau
2020-09-10 18:49 ` Andrii Nakryiko
2020-09-09 17:11 ` [PATCH bpf-next v2 04/11] bpf: allow specifying a BTF ID per argument in function protos Lorenz Bauer
2020-09-09 20:03 ` Martin KaFai Lau
2020-09-10 11:36 ` Lorenz Bauer
2020-09-10 18:51 ` Andrii Nakryiko
2020-09-09 17:11 ` [PATCH bpf-next v2 05/11] bpf: make BTF pointer type checking generic Lorenz Bauer
2020-09-09 20:15 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 06/11] bpf: make reference tracking generic Lorenz Bauer
2020-09-09 20:21 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 07/11] bpf: make context access check generic Lorenz Bauer
2020-09-09 20:42 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 08/11] bpf: set meta->raw_mode for pointers close to use Lorenz Bauer
2020-09-09 21:04 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 09/11] bpf: check ARG_PTR_TO_SPINLOCK register type in check_func_arg Lorenz Bauer
2020-09-09 21:14 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 10/11] bpf: hoist type checking for nullable arg types Lorenz Bauer
2020-09-09 21:28 ` Martin KaFai Lau
2020-09-09 17:11 ` [PATCH bpf-next v2 11/11] bpf: use a table to drive helper arg type checks Lorenz Bauer
2020-09-09 22:22 ` Martin KaFai Lau
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=20200909171155.256601-4-lmb@cloudflare.com \
--to=lmb@cloudflare.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@cloudflare.com \
--cc=yhs@fb.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