From: Rong Tao <rtoax@foxmail.com>
To: Quentin Monnet <qmo@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Andrew Kreimer <algonell@gmail.com>,
Rong Tao <rongtao@cestc.cn>, Lin Yikai <yikai.lin@vivo.com>,
bpf@vger.kernel.org (open list:BPF [TOOLING] (bpftool)),
linux-kernel@vger.kernel.org (open list)
Cc: rtoax@foxmail.com
Subject: [PATCH bpf-next 2/2] bpftool: skel: Introduce NAME__open_and_load_opts()
Date: Thu, 5 Jun 2025 15:51:13 +0800 [thread overview]
Message-ID: <tencent_F85EF146D110170D48845EB3F02ED5549409@qq.com> (raw)
In-Reply-To: <cover.1749109589.git.rongtao@cestc.cn>
From: Rong Tao <rongtao@cestc.cn>
Update Documentation for skel NAME__open_and_load_opts()
Signed-off-by: Rong Tao <rongtao@cestc.cn>
---
tools/bpf/bpftool/Documentation/bpftool-gen.rst | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/tools/bpf/bpftool/Documentation/bpftool-gen.rst b/tools/bpf/bpftool/Documentation/bpftool-gen.rst
index ca860fd97d8d..4dc2a624090e 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-gen.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-gen.rst
@@ -107,8 +107,10 @@ bpftool gen skeleton *FILE*
global data maps. It corresponds to libbpf's **bpf_object__load**\ ()
API.
- - **example__open_and_load** combines **example__open** and
- **example__load** invocations in one commonly used operation.
+ - **example__open_and_load** and **example__open_and_load_opts**.
+ Combines **example__open** and **example__load** invocations in one
+ commonly used operation. **_opts** variants accepts extra
+ **bpf_object_open_opts** options.
- **example__attach** and **example__detach**.
This pair of functions allow to attach and detach, correspondingly,
@@ -336,6 +338,9 @@ files into the final BPF ELF object file *example.bpf.o*.
const struct bpf_object_open_opts *opts);
static inline struct example *example__open();
static inline int example__load(struct example *obj);
+ static inline struct example *example__open();
+ static inline struct example *example__open_and_load_opts(
+ const struct bpf_object_open_opts *opts);
static inline struct example *example__open_and_load();
static inline int example__attach(struct example *obj);
static inline void example__detach(struct example *obj);
--
2.49.0
prev parent reply other threads:[~2025-06-05 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1749109589.git.rongtao@cestc.cn>
2025-06-05 7:51 ` [PATCH bpf-next 1/2] " Rong Tao
2025-06-05 16:45 ` Andrii Nakryiko
2025-06-05 7:51 ` Rong Tao [this message]
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=tencent_F85EF146D110170D48845EB3F02ED5549409@qq.com \
--to=rtoax@foxmail.com \
--cc=algonell@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=rongtao@cestc.cn \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yikai.lin@vivo.com \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®