From: wangyufen <wangyufen@huawei.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: <quentin@isovalent.com>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <martin.lau@linux.dev>, <song@kernel.org>,
<yhs@fb.com>, <john.fastabend@gmail.com>, <kpsingh@kernel.org>,
<sdf@google.com>, <haoluo@google.com>, <jolsa@kernel.org>,
<davem@davemloft.net>, <kuba@kernel.org>, <hawk@kernel.org>,
<nathan@kernel.org>, <ndesaulniers@google.com>, <trix@redhat.com>,
<bpf@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <llvm@lists.linux.dev>
Subject: Re: [bpf-next v7 1/3] bpftool: Add auto_attach for bpf prog load|loadall
Date: Sat, 8 Oct 2022 13:22:35 +0800 [thread overview]
Message-ID: <e2f2b01a-1f0e-a862-c3df-96f61dbdbaf6@huawei.com> (raw)
In-Reply-To: <CAEf4BzaBPpZvxD6sDMWWRXVqKYTgwaxsggye0CRbv7q5_4jrPA@mail.gmail.com>
在 2022/10/1 4:55, Andrii Nakryiko 写道:
> On Tue, Sep 27, 2022 at 4:00 AM Wang Yufen <wangyufen@huawei.com> wrote:
>> Add auto_attach optional to support one-step load-attach-pin_link.
>>
>> For example,
>> $ bpftool prog loadall test.o /sys/fs/bpf/test autoattach
>>
>> $ bpftool link
>> 26: tracing name test1 tag f0da7d0058c00236 gpl
>> loaded_at 2022-09-09T21:39:49+0800 uid 0
>> xlated 88B jited 55B memlock 4096B map_ids 3
>> btf_id 55
>> 28: kprobe name test3 tag 002ef1bef0723833 gpl
>> loaded_at 2022-09-09T21:39:49+0800 uid 0
>> xlated 88B jited 56B memlock 4096B map_ids 3
>> btf_id 55
>> 57: tracepoint name oncpu tag 7aa55dfbdcb78941 gpl
>> loaded_at 2022-09-09T21:41:32+0800 uid 0
>> xlated 456B jited 265B memlock 4096B map_ids 17,13,14,15
>> btf_id 82
>>
>> $ bpftool link
>> 1: tracing prog 26
>> prog_type tracing attach_type trace_fentry
>> 3: perf_event prog 28
>> 10: perf_event prog 57
>>
>> The autoattach optional can support tracepoints, k(ret)probes,
>> u(ret)probes.
>>
>> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
>> Signed-off-by: Wang Yufen <wangyufen@huawei.com>
>> ---
> For next revision, please also attach cover letter describing the
> overall goal of the patch set (and that's where the version log
> between revisions is put as well).
Thanks, will add a cover letter in v8.
>
>
>> v6 -> v7: add info msg print and update doc for the skip program
>> v5 -> v6: skip the programs not supporting auto-attach,
>> and change optional name from "auto_attach" to "autoattach"
>> v4 -> v5: some formatting nits of doc
>> v3 -> v4: rename functions, update doc, bash and do_help()
>> v2 -> v3: switch to extend prog load command instead of extend perf
>> v2: https://patchwork.kernel.org/project/netdevbpf/patch/20220824033837.458197-1-weiyongjun1@huawei.com/
>> v1: https://patchwork.kernel.org/project/netdevbpf/patch/20220816151725.153343-1-weiyongjun1@huawei.com/
>> tools/bpf/bpftool/prog.c | 81 ++++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 79 insertions(+), 2 deletions(-)
>>
> [...]
>
prev parent reply other threads:[~2022-10-08 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 11:21 Wang Yufen
2022-09-27 11:21 ` [bpf-next v7 2/3] bpftool: Update doc (add autoattach to prog load) Wang Yufen
2022-09-30 16:27 ` Quentin Monnet
2022-09-27 11:21 ` [bpf-next v7 3/3] bpftool: Update the bash completion(add " Wang Yufen
2022-09-30 16:26 ` [bpf-next v7 1/3] bpftool: Add auto_attach for bpf prog load|loadall Quentin Monnet
2022-10-08 5:16 ` wangyufen
2022-10-10 8:40 ` Quentin Monnet
2022-10-10 8:58 ` wangyufen
2022-09-30 20:55 ` Andrii Nakryiko
2022-10-08 5:22 ` wangyufen [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=e2f2b01a-1f0e-a862-c3df-96f61dbdbaf6@huawei.com \
--to=wangyufen@huawei.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=trix@redhat.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
all inboxes | Powered by JetHome®