From: Yafang Shao <laoar.shao@gmail.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: 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, quentin@isovalent.com, bpf@vger.kernel.org,
Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Subject: Re: [PATCH v2 bpf-next 09/11] libbpf: Add perf event names
Date: Sun, 11 Jun 2023 23:55:07 +0800 [thread overview]
Message-ID: <CALOAHbBFQZm=c9Dsmztk_RFM7_HbDMZFV0+u0Djzq9WM-xXXCw@mail.gmail.com> (raw)
In-Reply-To: <ZIT8qWzkl6P2wXmq@krava>
On Sun, Jun 11, 2023 at 6:43 AM Jiri Olsa <olsajiri@gmail.com> wrote:
>
> On Thu, Jun 08, 2023 at 10:35:21AM +0000, Yafang Shao wrote:
> > Add libbpf API to get generic perf event name.
> >
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> > ---
> > tools/lib/bpf/libbpf.c | 107 +++++++++++++++++++++++++++++++++++++++++++++++
> > tools/lib/bpf/libbpf.h | 56 +++++++++++++++++++++++++
> > tools/lib/bpf/libbpf.map | 6 +++
> > 3 files changed, 169 insertions(+)
> >
> > diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> > index 47632606..27d396f 100644
> > --- a/tools/lib/bpf/libbpf.c
> > +++ b/tools/lib/bpf/libbpf.c
> > @@ -119,6 +119,64 @@
> > [BPF_STRUCT_OPS] = "struct_ops",
> > };
> >
> > +static const char * const perf_type_name[] = {
> > + [PERF_TYPE_HARDWARE] = "hardware",
> > + [PERF_TYPE_SOFTWARE] = "software",
> > + [PERF_TYPE_TRACEPOINT] = "tracepoint",
> > + [PERF_TYPE_HW_CACHE] = "hw_cache",
> > + [PERF_TYPE_RAW] = "raw",
> > + [PERF_TYPE_BREAKPOINT] = "breakpoint",
> > +};
> > +
> > +static const char * const perf_hw_name[] = {
> > + [PERF_COUNT_HW_CPU_CYCLES] = "cpu_cycles",
>
> could you use '-' instead of '_' because that's what we do in perf
>
> actually would be great if you could use same names like in
> tool/perf/util/parse-events.c 'event_symbols_*' arrays
> tool/perf/util/evsel.c 'evsel__hw_cache' array
>
> so perf and bpftool would use same names and we have a chance
> to use same code for that in future
Good point. Will copy them :)
--
Regards
Yafang
next prev parent reply other threads:[~2023-06-11 15:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 10:35 [PATCH v2 bpf-next 00/11] bpf: Support ->fill_link_info for kprobe_multi and perf_event links Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 01/11] bpf: Support ->fill_link_info for kprobe_multi Yafang Shao
2023-06-08 23:05 ` Andrii Nakryiko
2023-06-09 9:13 ` Yafang Shao
2023-06-09 18:25 ` Andrii Nakryiko
2023-06-10 2:19 ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 02/11] bpftool: Add address filtering in kernel_syms_load() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 03/11] bpftool: Show probed function in kprobe_multi link info Yafang Shao
2023-06-08 23:08 ` Andrii Nakryiko
2023-06-09 9:15 ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 04/11] bpf: Protect probed address based on kptr_restrict setting Yafang Shao
2023-06-08 23:08 ` Andrii Nakryiko
2023-06-09 9:16 ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 05/11] bpf: Clear the probe_addr for uprobe Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 06/11] bpf: Expose symbol addresses for precise identification Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 07/11] bpf: Add a common helper bpf_copy_to_user() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 08/11] bpf: Support ->fill_link_info for perf_event Yafang Shao
2023-06-08 23:12 ` Andrii Nakryiko
2023-06-09 9:53 ` Yafang Shao
2023-06-09 9:56 ` Yafang Shao
2023-06-09 18:26 ` Andrii Nakryiko
2023-06-10 2:21 ` Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 09/11] libbpf: Add perf event names Yafang Shao
2023-06-08 23:14 ` Andrii Nakryiko
2023-06-09 4:36 ` Song Liu
2023-06-10 2:22 ` Yafang Shao
2023-06-10 20:34 ` Quentin Monnet
2023-06-11 15:52 ` Yafang Shao
2023-06-10 22:37 ` Jiri Olsa
2023-06-10 22:43 ` Jiri Olsa
2023-06-11 15:55 ` Yafang Shao [this message]
2023-06-08 10:35 ` [PATCH v2 bpf-next 10/11] bpftool: Move get_prog_info() into do_show_link() Yafang Shao
2023-06-08 10:35 ` [PATCH v2 bpf-next 11/11] bpftool: Show probed function in perf_event 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='CALOAHbBFQZm=c9Dsmztk_RFM7_HbDMZFV0+u0Djzq9WM-xXXCw@mail.gmail.com' \
--to=laoar.shao@gmail.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=olsajiri@gmail.com \
--cc=quentin@isovalent.com \
--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).