From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>,
Ian Rogers <irogers@google.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>
Subject: [PATCHv2 00/13] perf tests: Add metrics tests
Date: Tue, 2 Jun 2020 13:50:42 +0200 [thread overview]
Message-ID: <20200602115055.1168446-1-jolsa@kernel.org> (raw)
hi,
changes for using metric result in another metric seem
to change lot of core metric code, so it's better we
have some more tests before we do that.
v2 changes:
- some of the patches got accepted
- add missing free to patch 1 [Ian]
- factor pmu-events test functions and reuse it in the new test [Ian]
- add fake_pmu bool to parse_events interface [Ian]
- simplify metric tests
- use proper cover letter subject ;-)
I actually reworked the 2 patches Ian acked so far,
so I did not add them.
Also available in here:
git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/metric_test
thanks,
jirka
---
Jiri Olsa (13):
perf tools: Add fake pmu support
perf tools: Add fake_pmu bool to parse_events interface
perf tests: Factor check_parse_id function
perf tests: Add another metric parsing test
perf tools: Factor out parse_groups function
perf tools: Add fake_pmu to parse_events function
perf tools: Add map to parse_events function
perf tools: Add metricgroup__parse_groups_test function
perf tools: Factor out prepare_metric function
perf tools: Release metric_events rblist
perf tools: Add test_generic_metric function
perf tests: Add parse metric test for ipc metric
perf tests: Add parse metric test for frontend metric
tools/perf/arch/arm/util/cs-etm.c | 2 +-
tools/perf/arch/arm64/util/arm-spe.c | 2 +-
tools/perf/arch/powerpc/util/kvm-stat.c | 2 +-
tools/perf/arch/x86/tests/intel-cqm.c | 2 +-
tools/perf/arch/x86/tests/perf-time-to-tsc.c | 2 +-
tools/perf/arch/x86/util/intel-bts.c | 2 +-
tools/perf/arch/x86/util/intel-pt.c | 6 ++--
tools/perf/builtin-stat.c | 9 +++---
tools/perf/builtin-trace.c | 4 +--
tools/perf/tests/Build | 1 +
tools/perf/tests/backward-ring-buffer.c | 3 +-
tools/perf/tests/builtin-test.c | 4 +++
tools/perf/tests/code-reading.c | 2 +-
tools/perf/tests/event-times.c | 2 +-
tools/perf/tests/evsel-roundtrip-name.c | 4 +--
tools/perf/tests/hists_cumulate.c | 2 +-
tools/perf/tests/hists_filter.c | 4 +--
tools/perf/tests/hists_link.c | 4 +--
tools/perf/tests/hists_output.c | 2 +-
tools/perf/tests/keep-tracking.c | 4 +--
tools/perf/tests/parse-events.c | 2 +-
tools/perf/tests/parse-metric.c | 170 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tools/perf/tests/pmu-events.c | 132 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
tools/perf/tests/switch-tracking.c | 8 ++---
tools/perf/tests/tests.h | 1 +
tools/perf/util/bpf-loader.c | 2 +-
tools/perf/util/metricgroup.c | 74 ++++++++++++++++++++++++++++++++++++----------
tools/perf/util/metricgroup.h | 10 +++++++
tools/perf/util/parse-events.c | 29 +++++++++++-------
tools/perf/util/parse-events.h | 5 ++--
tools/perf/util/parse-events.l | 8 +++--
tools/perf/util/parse-events.y | 41 ++++++++++++++++++++++++--
tools/perf/util/perf_api_probe.c | 2 +-
tools/perf/util/record.c | 2 +-
tools/perf/util/stat-shadow.c | 67 ++++++++++++++++++++++++++++++------------
tools/perf/util/stat.h | 3 ++
36 files changed, 527 insertions(+), 92 deletions(-)
create mode 100644 tools/perf/tests/parse-metric.c
next reply other threads:[~2020-06-02 11:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 11:50 Jiri Olsa [this message]
2020-06-02 11:50 ` [PATCH 01/13] perf tools: Add fake pmu support Jiri Olsa
2020-06-02 11:50 ` [PATCH 02/13] perf tools: Add fake_pmu bool to parse_events interface Jiri Olsa
2020-06-02 11:50 ` [PATCH 03/13] perf tests: Factor check_parse_id function Jiri Olsa
2020-06-02 11:50 ` [PATCH 04/13] perf tests: Add another metric parsing test Jiri Olsa
2020-06-02 17:58 ` Ian Rogers
2020-06-02 19:03 ` Jiri Olsa
2020-06-02 19:08 ` Jiri Olsa
2020-06-02 20:30 ` Ian Rogers
2020-06-02 11:50 ` [PATCH 05/13] perf tools: Factor out parse_groups function Jiri Olsa
2020-06-02 11:50 ` [PATCH 06/13] perf tools: Add fake_pmu to parse_events function Jiri Olsa
2020-06-02 11:50 ` [PATCH 07/13] perf tools: Add map " Jiri Olsa
2020-06-02 11:50 ` [PATCH 08/13] perf tools: Add metricgroup__parse_groups_test function Jiri Olsa
2020-06-02 11:50 ` [PATCH 09/13] perf tools: Factor out prepare_metric function Jiri Olsa
2020-06-02 11:50 ` [PATCH 10/13] perf tools: Release metric_events rblist Jiri Olsa
2020-06-02 11:50 ` [PATCH 11/13] perf tools: Add test_generic_metric function Jiri Olsa
2020-06-02 11:50 ` [PATCH 12/13] perf tests: Add parse metric test for ipc metric Jiri Olsa
2020-06-02 11:50 ` [PATCH 13/13] perf tests: Add parse metric test for frontend metric Jiri Olsa
2020-06-02 18:10 ` [PATCHv2 00/13] perf tests: Add metrics tests Ian Rogers
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=20200602115055.1168446-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
/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).