From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>, Andrii Nakryiko <andriin@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>, Kajol Jain <kjain@linux.ibm.com>,
Andi Kleen <ak@linux.intel.com>,
John Garry <john.garry@huawei.com>,
Jin Yao <yao.jin@linux.intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Kim Phillips <kim.phillips@amd.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Leo Yan <leo.yan@linaro.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v2 0/7] Copy hashmap to tools/perf/util, use in perf expr
Date: Fri, 15 May 2020 14:00:36 -0300 [thread overview]
Message-ID: <20200515170036.GA10230@kernel.org> (raw)
In-Reply-To: <20200515165007.217120-1-irogers@google.com>
Em Fri, May 15, 2020 at 09:50:00AM -0700, Ian Rogers escreveu:
> Perf's expr code currently builds an array of strings then removes
> duplicates. The array is larger than necessary and has recently been
> increased in size. When this was done it was commented that a hashmap
> would be preferable.
>
> libbpf has a hashmap but libbpf isn't currently required to build
> perf. To satisfy various concerns this change copies libbpf's hashmap
> into tools/perf/util, it then adds a check in perf that the two are in
> sync.
>
> Andrii's patch to hashmap from bpf-next is brought into this set to
> fix issues with hashmap__clear.
>
> Two minor changes to libbpf's hashmap are made that remove an unused
> dependency and fix a compiler warning.
Andrii/Alexei/Daniel, what do you think about me merging these fixes in my
perf-tools-next branch?
- Arnaldo
> Two perf test changes are also brought in as they need refactoring to
> account for the expr API change and it is expected they will land
> ahead of this.
> https://lore.kernel.org/lkml/20200513062236.854-2-irogers@google.com/
>
> Tested with 'perf test' and 'make -C tools/perf build-test'.
>
> The hashmap change was originally part of an RFC:
> https://lore.kernel.org/lkml/20200508053629.210324-1-irogers@google.com/
>
> v2. moves hashmap into tools/perf/util rather than libapi, to allow
> hashmap's libbpf symbols to be visible when built statically for
> testing.
>
> Andrii Nakryiko (1):
> libbpf: Fix memory leak and possible double-free in hashmap__clear
>
> Ian Rogers (6):
> libbpf hashmap: Remove unused #include
> libbpf hashmap: Fix signedness warnings
> tools lib/api: Copy libbpf hashmap to tools/perf/util
> perf test: Provide a subtest callback to ask for the reason for
> skipping a subtest
> perf test: Improve pmu event metric testing
> perf expr: Migrate expr ids table to a hashmap
>
> tools/lib/bpf/hashmap.c | 10 +-
> tools/lib/bpf/hashmap.h | 1 -
> tools/perf/check-headers.sh | 4 +
> tools/perf/tests/builtin-test.c | 18 ++-
> tools/perf/tests/expr.c | 40 +++---
> tools/perf/tests/pmu-events.c | 169 ++++++++++++++++++++++-
> tools/perf/tests/tests.h | 4 +
> tools/perf/util/Build | 4 +
> tools/perf/util/expr.c | 129 +++++++++--------
> tools/perf/util/expr.h | 26 ++--
> tools/perf/util/expr.y | 22 +--
> tools/perf/util/hashmap.c | 238 ++++++++++++++++++++++++++++++++
> tools/perf/util/hashmap.h | 177 ++++++++++++++++++++++++
> tools/perf/util/metricgroup.c | 87 ++++++------
> tools/perf/util/stat-shadow.c | 49 ++++---
> 15 files changed, 798 insertions(+), 180 deletions(-)
> create mode 100644 tools/perf/util/hashmap.c
> create mode 100644 tools/perf/util/hashmap.h
>
> --
> 2.26.2.761.g0e0b3e54be-goog
>
--
- Arnaldo
next prev parent reply other threads:[~2020-05-15 17:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 16:50 [PATCH v2 0/7] Copy hashmap to tools/perf/util, use in perf expr Ian Rogers
2020-05-15 16:50 ` [PATCH v2 1/7] libbpf: Fix memory leak and possible double-free in hashmap__clear Ian Rogers
2020-05-15 16:50 ` [PATCH v2 2/7] libbpf hashmap: Remove unused #include Ian Rogers
2020-05-15 19:39 ` Andrii Nakryiko
2020-05-15 16:50 ` [PATCH v2 3/7] libbpf hashmap: Fix signedness warnings Ian Rogers
2020-05-15 19:40 ` Andrii Nakryiko
2020-05-15 16:50 ` [PATCH v2 4/7] tools lib/api: Copy libbpf hashmap to tools/perf/util Ian Rogers
2020-05-15 19:41 ` Andrii Nakryiko
2020-05-15 16:50 ` [PATCH v2 5/7] perf test: Provide a subtest callback to ask for the reason for skipping a subtest Ian Rogers
2020-05-15 16:50 ` [PATCH v2 6/7] perf test: Improve pmu event metric testing Ian Rogers
2020-05-15 16:50 ` [PATCH v2 7/7] perf expr: Migrate expr ids table to a hashmap Ian Rogers
2020-05-15 19:39 ` Andrii Nakryiko
2020-05-15 22:03 ` Ian Rogers
2020-05-15 19:41 ` Jiri Olsa
2020-05-15 21:35 ` Ian Rogers
2020-05-15 22:41 ` Jiri Olsa
2020-05-15 22:41 ` Jiri Olsa
2020-05-15 22:59 ` Ian Rogers
2020-05-15 17:00 ` Arnaldo Carvalho de Melo [this message]
2020-05-15 19:42 ` [PATCH v2 0/7] Copy hashmap to tools/perf/util, use in perf expr Andrii Nakryiko
2020-05-15 21:18 ` arnaldo.melo
2020-05-15 21:47 ` Ian Rogers
2020-05-15 23:09 ` Daniel Borkmann
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=20200515170036.GA10230@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=john.fastabend@gmail.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kan.liang@linux.intel.com \
--cc=kim.phillips@amd.com \
--cc=kjain@linux.ibm.com \
--cc=kpsingh@chromium.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yao.jin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).