From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"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>,
"Ian Rogers" <irogers@google.com>,
"Vijay Thakkar" <vijaythakkar@me.com>,
"Martin Liška" <mliska@suse.cz>,
"Michael Petlan" <mpetlan@redhat.com>,
"Kim Phillips" <kim.phillips@amd.com>
Subject: Re: [PATCH 0/4] perf events vendor amd: Fixes, cleanups and updates for AMD Zen cores
Date: Wed, 7 Apr 2021 10:30:22 -0300 [thread overview]
Message-ID: <YG2z7q6MhhxO+M9p@kernel.org> (raw)
In-Reply-To: <20210406215944.113332-1-Smita.KoralahalliChannabasappa@amd.com>
Em Tue, Apr 06, 2021 at 04:59:40PM -0500, Smita Koralahalli escreveu:
> This series of patches provides a fix for the broken metric and does some
> cleanup for AMD Zen1/Zen2 cores. Additionally, adds Zen3 events.
>
> The first patch fixes broken L2 Cache Hits from L2 HWPF recommended event.
>
> The second and third patches addresses the inconsistency by defaulting all
> event codes and umask values to use lower cases and 0x%02x as their
> format.
>
> The final patch adds Zen3 events.
Thanks, applied.
- Arnaldo
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Jiri Olsa <jolsa@redhat.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Ian Rogers <irogers@google.com>
> Cc: Vijay Thakkar <vijaythakkar@me.com>
> Cc: Martin Liška <mliska@suse.cz>
> Cc: Michael Petlan <mpetlan@redhat.com>
> Cc: Kim Phillips <kim.phillips@amd.com>
> Cc: linux-perf-users@vger.kernel.org
>
> Smita Koralahalli (4):
> perf vendor events amd: Fix broken L2 Cache Hits from L2 HWPF metric
> perf vendor events amd: Use lowercases for all the eventcodes and umasks
> perf vendor events amd: Use 0x%02x format for event code and umask
> perf vendor events amd: Add Zen3 events
>
> .../pmu-events/arch/x86/amdzen1/cache.json | 48 +-
> .../pmu-events/arch/x86/amdzen1/core.json | 12 +-
> .../arch/x86/amdzen1/floating-point.json | 42 +-
> .../pmu-events/arch/x86/amdzen1/memory.json | 42 +-
> .../pmu-events/arch/x86/amdzen1/other.json | 12 +-
> .../arch/x86/amdzen1/recommended.json | 8 +-
> .../pmu-events/arch/x86/amdzen2/branch.json | 8 +-
> .../pmu-events/arch/x86/amdzen2/cache.json | 60 +--
> .../pmu-events/arch/x86/amdzen2/core.json | 12 +-
> .../arch/x86/amdzen2/floating-point.json | 42 +-
> .../pmu-events/arch/x86/amdzen2/memory.json | 86 ++--
> .../pmu-events/arch/x86/amdzen2/other.json | 20 +-
> .../arch/x86/amdzen2/recommended.json | 8 +-
> .../pmu-events/arch/x86/amdzen3/branch.json | 53 +++
> .../pmu-events/arch/x86/amdzen3/cache.json | 402 ++++++++++++++++
> .../pmu-events/arch/x86/amdzen3/core.json | 137 ++++++
> .../arch/x86/amdzen3/data-fabric.json | 98 ++++
> .../arch/x86/amdzen3/floating-point.json | 139 ++++++
> .../pmu-events/arch/x86/amdzen3/memory.json | 428 ++++++++++++++++++
> .../pmu-events/arch/x86/amdzen3/other.json | 103 +++++
> .../arch/x86/amdzen3/recommended.json | 214 +++++++++
> tools/perf/pmu-events/arch/x86/mapfile.csv | 2 +-
> 22 files changed, 1775 insertions(+), 201 deletions(-)
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/branch.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/cache.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/core.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/data-fabric.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/floating-point.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/memory.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/other.json
> create mode 100644 tools/perf/pmu-events/arch/x86/amdzen3/recommended.json
>
> --
> 2.17.1
>
--
- Arnaldo
prev parent reply other threads:[~2021-04-07 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 21:59 [PATCH 0/4] perf events vendor amd: Fixes, cleanups and updates for AMD Zen cores Smita Koralahalli
2021-04-06 21:59 ` [PATCH 1/4] perf vendor events amd: Fix broken L2 Cache Hits from L2 HWPF metric Smita Koralahalli
2021-04-06 21:59 ` [PATCH 2/4] perf vendor events amd: Use lowercases for all the eventcodes and umasks Smita Koralahalli
2021-04-06 21:59 ` [PATCH 3/4] perf vendor events amd: Use 0x%02x format for event code and umask Smita Koralahalli
2021-04-06 21:59 ` [PATCH 4/4] perf vendor events amd: Add Zen3 events Smita Koralahalli
2021-04-07 13:30 ` 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=YG2z7q6MhhxO+M9p@kernel.org \
--to=acme@kernel.org \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=mpetlan@redhat.com \
--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