From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Jin Yao <yao.jin@linux.intel.com>,
John Garry <john.garry@huawei.com>, Paul Clarke <pc@us.ibm.com>,
kajoljain <kjain@linux.ibm.com>
Cc: Stephane Eranian <eranian@google.com>,
Sandeep Dasgupta <sdasgup@google.com>,
linux-perf-users@vger.kernel.org, Ian Rogers <irogers@google.com>
Subject: [RFC PATCH 00/12] Topdown parser
Date: Tue, 10 Nov 2020 02:03:34 -0800 [thread overview]
Message-ID: <20201110100346.2527031-1-irogers@google.com> (raw)
This RFC is for a new tool that reads TMA_Metrics.csv as found on
download.01.org/perfmon and generates metrics and metric groups from
it. To show the functionality the TMA_Metrics.csv is downloaded, but
an accepted change would most likely include a copy of this file from
Intel. With this tool rather than just level 1 topdown metrics, a full
set of topdown metrics to level 4 are generated.
This change was:
Suggested-by: Stephane Eranian <eranian@google.com>
Sandeep Dasgupta (12):
perf topdown-parser: Add a simple logging API.
perf topdown-parser: Add utility functions.
perf topdown-paser: Add a CSV file reader.
perf topdown-parser: Add a json file reader.
perf topdown-parser: Add a configuration.
perf topdown-parser: Interface for TMA_Metrics.csv.
perf topdown-parser: Metric expression parser.
perf topdown-parser: Add event interface.
perf topdown-paser: Add code generation API.
perf topdown-parser: Add json metric code generation.
perf topdown-parser: Main driver.
perf pmu-events: Topdown parser tool
tools/perf/Makefile.perf | 13 +-
tools/perf/pmu-events/Build | 50 +-
tools/perf/pmu-events/topdown-parser/README | 5 +
.../topdown-parser/code_gen_target.cpp | 51 +
.../topdown-parser/code_gen_target.h | 77 ++
.../code_gen_target_perf_json.cpp | 546 ++++++++++
.../code_gen_target_perf_json.h | 25 +
.../topdown-parser/configuration.cpp | 198 ++++
.../pmu-events/topdown-parser/configuration.h | 181 ++++
.../topdown-parser/configuration.json | 72 ++
.../pmu-events/topdown-parser/csvreader.cpp | 49 +
.../pmu-events/topdown-parser/csvreader.h | 51 +
.../topdown-parser/dependence_dag_utils.cpp | 984 ++++++++++++++++++
.../topdown-parser/dependence_dag_utils.h | 178 ++++
.../pmu-events/topdown-parser/event_info.cpp | 443 ++++++++
.../pmu-events/topdown-parser/event_info.h | 114 ++
.../pmu-events/topdown-parser/expr_parser.y | 224 ++++
.../topdown-parser/general_utils.cpp | 173 +++
.../pmu-events/topdown-parser/general_utils.h | 131 +++
.../pmu-events/topdown-parser/jsmn_extras.cpp | 199 ++++
.../pmu-events/topdown-parser/jsmn_extras.h | 42 +
.../perf/pmu-events/topdown-parser/logging.h | 25 +
.../topdown-parser/topdown_parser_main.cpp | 155 +++
23 files changed, 3981 insertions(+), 5 deletions(-)
create mode 100644 tools/perf/pmu-events/topdown-parser/README
create mode 100644 tools/perf/pmu-events/topdown-parser/code_gen_target.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/code_gen_target.h
create mode 100644 tools/perf/pmu-events/topdown-parser/code_gen_target_perf_json.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/code_gen_target_perf_json.h
create mode 100644 tools/perf/pmu-events/topdown-parser/configuration.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/configuration.h
create mode 100644 tools/perf/pmu-events/topdown-parser/configuration.json
create mode 100644 tools/perf/pmu-events/topdown-parser/csvreader.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/csvreader.h
create mode 100644 tools/perf/pmu-events/topdown-parser/dependence_dag_utils.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/dependence_dag_utils.h
create mode 100644 tools/perf/pmu-events/topdown-parser/event_info.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/event_info.h
create mode 100644 tools/perf/pmu-events/topdown-parser/expr_parser.y
create mode 100644 tools/perf/pmu-events/topdown-parser/general_utils.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/general_utils.h
create mode 100644 tools/perf/pmu-events/topdown-parser/jsmn_extras.cpp
create mode 100644 tools/perf/pmu-events/topdown-parser/jsmn_extras.h
create mode 100644 tools/perf/pmu-events/topdown-parser/logging.h
create mode 100644 tools/perf/pmu-events/topdown-parser/topdown_parser_main.cpp
--
2.29.2.222.g5d2a92d10f8-goog
next reply other threads:[~2020-11-10 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:03 Ian Rogers [this message]
2020-11-10 10:03 ` [RFC PATCH 01/12] perf topdown-parser: Add a simple logging API Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 02/12] perf topdown-parser: Add utility functions Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 03/12] perf topdown-paser: Add a CSV file reader Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 04/12] perf topdown-parser: Add a json " Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 05/12] perf topdown-parser: Add a configuration Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 06/12] perf topdown-parser: Interface for TMA_Metrics.csv Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 07/12] perf topdown-parser: Metric expression parser Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 08/12] perf topdown-parser: Add event interface Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 09/12] perf topdown-paser: Add code generation API Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 10/12] perf topdown-parser: Add json metric code generation Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 11/12] perf topdown-parser: Main driver Ian Rogers
2020-11-10 10:03 ` [RFC PATCH 12/12] perf pmu-events: Topdown parser tool Ian Rogers
2020-11-11 21:46 ` [RFC PATCH 00/12] Topdown parser Andi Kleen
[not found] ` <CAP-5=fXedJEZcYhxmPAzRVx5kdW2YA71Ks3BycqurAHydtXh8A@mail.gmail.com>
2020-11-12 3:10 ` Andi Kleen
[not found] ` <CAP-5=fUDOLzfpuJNjk_D6KrAGMNXKXOFKfVi9O7qXRDdP_4Rpg@mail.gmail.com>
2020-11-12 6:35 ` Andi Kleen
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=20201110100346.2527031-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--cc=peterz@infradead.org \
--cc=sdasgup@google.com \
--cc=yao.jin@linux.intel.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