From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, Yonghong Song <yhs@fb.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Quentin Monnet <quentin@isovalent.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>, bpf <bpf@vger.kernel.org>,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v4 bpf-next 09/11] bpf: Support ->fill_link_info for perf_event
Date: Tue, 20 Jun 2023 14:22:00 -0700 [thread overview]
Message-ID: <CAADnVQLjaKbe6JgPFe+=dJWxmNwdo9rQzCjvoqJ9Frn_DOSpCw@mail.gmail.com> (raw)
In-Reply-To: <20230620163008.3718-10-laoar.shao@gmail.com>
On Tue, Jun 20, 2023 at 9:30 AM Yafang Shao <laoar.shao@gmail.com> wrote:
>
> +enum bpf_perf_event_type {
> + BPF_PERF_EVENT_UNSPEC = 0,
> + BPF_PERF_EVENT_UPROBE = 1,
> + BPF_PERF_EVENT_KPROBE = 2,
> + BPF_PERF_EVENT_TRACEPOINT = 3,
> + BPF_PERF_EVENT_EVENT = 4,
> +
> + MAX_BPF_PERF_EVENT_TYPE,
> +};
afaics MAX_BPF_PERF_EVENT_TYPE is completely unused.
Every patch should be focusing on minimizing additions to uapi.
next prev parent reply other threads:[~2023-06-20 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 16:29 [PATCH v4 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links Yafang Shao
2023-06-20 16:29 ` [PATCH v4 bpf-next 01/11] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-06-20 16:29 ` [PATCH v4 bpf-next 02/11] bpftool: Dump the kernel symbol's module name Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 03/11] bpftool: Show kprobe_multi link info Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 04/11] bpf: Protect probed address based on kptr_restrict setting Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 05/11] bpf: Clear the probe_addr for uprobe Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 06/11] bpf: Expose symbol's respective address Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 07/11] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 08/11] bpf: Add bpf_perf_link_fill_common() Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 09/11] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-06-20 21:22 ` Alexei Starovoitov [this message]
2023-06-21 1:29 ` Yafang Shao
2023-06-21 23:00 ` Yonghong Song
2023-06-22 0:54 ` Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 10/11] bpftool: Add perf event names Yafang Shao
2023-06-20 16:30 ` [PATCH v4 bpf-next 11/11] bpftool: Show perf link info Yafang Shao
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='CAADnVQLjaKbe6JgPFe+=dJWxmNwdo9rQzCjvoqJ9Frn_DOSpCw@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mhiramat@kernel.org \
--cc=quentin@isovalent.com \
--cc=rostedt@goodmis.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).