From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Vijay Thakkar <vijaythakkar@me.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Kim Phillips" <kim.phillips@amd.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
"Martin Liška" <mliska@suse.cz>, "Jon Grimm" <jon.grimm@amd.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v6 0/3] perf vendor events amd: latest PMU events for zen1/zen2
Date: Wed, 18 Mar 2020 17:04:43 -0300 [thread overview]
Message-ID: <20200318200443.GA29668@kernel.org> (raw)
In-Reply-To: <20200318190002.307290-1-vijaythakkar@me.com>
Em Wed, Mar 18, 2020 at 02:59:59PM -0400, Vijay Thakkar escreveu:
> This series of patches brings the PMU events for AMD family 17h series
> of processors up to date with the latest versions of the AMD processor
> programming reference manuals.
>
> The first patch changes the pmu events mapfile to be more selective for
> the model number rather than blanket detecting all f17h processors to
> have the same events directory. This is required for the later patch
> where we add events for zen2 based processors.
>
> The second patch adds the PMU events for zen2.
Thanks, re-tested and applied.
- Arnaldo
> Finally the third patch updates the zen1 PMU events to be in accordance
> with the latest PPR version and bumps up the events version to v2.
>
> Vijay Thakkar (3):
> perf vendor events amd: restrict model detection for zen1 based
> processors
> perf vendor events amd: add Zen2 events
> perf vendor events amd: update Zen1 events to V2
>
> .../pmu-events/arch/x86/amdfam17h/branch.json | 12 -
> .../pmu-events/arch/x86/amdfam17h/cache.json | 329 -----------------
> .../pmu-events/arch/x86/amdfam17h/other.json | 65 ----
> .../pmu-events/arch/x86/amdzen1/branch.json | 23 ++
> .../pmu-events/arch/x86/amdzen1/cache.json | 294 +++++++++++++++
> .../arch/x86/{amdfam17h => amdzen1}/core.json | 15 +-
> .../floating-point.json | 64 +++-
> .../x86/{amdfam17h => amdzen1}/memory.json | 82 +++--
> .../pmu-events/arch/x86/amdzen1/other.json | 56 +++
> .../pmu-events/arch/x86/amdzen2/branch.json | 52 +++
> .../pmu-events/arch/x86/amdzen2/cache.json | 338 +++++++++++++++++
> .../pmu-events/arch/x86/amdzen2/core.json | 130 +++++++
> .../arch/x86/amdzen2/floating-point.json | 140 +++++++
> .../pmu-events/arch/x86/amdzen2/memory.json | 341 ++++++++++++++++++
> .../pmu-events/arch/x86/amdzen2/other.json | 115 ++++++
> tools/perf/pmu-events/arch/x86/mapfile.csv | 3 +-
> 16 files changed, 1606 insertions(+), 453 deletions(-)
> delete mode 100644 tools/perf/pmu-events/arch/x86/amdfam17h/branch.json
> delete mode 100644 tools/perf/pmu-events/arch/x86/amdfam17h/cache.json
> delete mode 100644 tools/perf/pmu-events/arch/x86/amdfam17h/other.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen1/branch.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen1/cache.json
> rename tools/perf/pmu-events/arch/x86/{amdfam17h => amdzen1}/core.json (87%)
> rename tools/perf/pmu-events/arch/x86/{amdfam17h => amdzen1}/floating-point.json (61%)
> rename tools/perf/pmu-events/arch/x86/{amdfam17h => amdzen1}/memory.json (63%)
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen1/other.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/branch.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/cache.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/core.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/floating-point.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/memory.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen2/other.json
>
> --
> 2.25.2
>
--
- Arnaldo
prev parent reply other threads:[~2020-03-18 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 18:59 [PATCH v6 0/3] perf vendor events amd: latest PMU events for zen1/zen2 Vijay Thakkar
2020-03-18 19:00 ` [PATCH v6 1/3] perf vendor events amd: restrict model detection for zen1 based processors Vijay Thakkar
2020-04-04 8:41 ` [tip: perf/urgent] perf vendor events amd: Restrict " tip-bot2 for Vijay Thakkar
2020-03-18 19:00 ` [PATCH v6 2/3] perf vendor events amd: add Zen2 events Vijay Thakkar
2020-04-04 8:41 ` [tip: perf/urgent] perf vendor events amd: Add " tip-bot2 for Vijay Thakkar
2020-03-18 19:00 ` [PATCH v6 3/3] perf vendor events amd: update Zen1 events to V2 Vijay Thakkar
2020-04-04 8:41 ` [tip: perf/urgent] perf vendor events amd: Update " tip-bot2 for Vijay Thakkar
2020-03-18 20:04 ` Arnaldo Carvalho de Melo [this message]
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=20200318200443.GA29668@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=jon.grimm@amd.com \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=vijaythakkar@me.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).