From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Sandipan Das <sandipan.das@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
namhyung@kernel.org, eranian@google.com, jhladky@redhat.com,
ravi.bangoria@amd.com, ananth.narayan@amd.com
Subject: Re: [PATCH v2 0/4] perf vendor events amd: Add Zen 4 events and metrics
Date: Wed, 21 Dec 2022 14:03:09 -0300 [thread overview]
Message-ID: <Y6M8TeUR73AB+TKP@kernel.org> (raw)
In-Reply-To: <CAP-5=fWm55y6LdZozX=LuLZhk+SWm_yi5tLcKgT_UJt9FETNPQ@mail.gmail.com>
Em Wed, Dec 14, 2022 at 07:59:01AM -0800, Ian Rogers escreveu:
> On Wed, Dec 14, 2022 at 12:27 AM Sandipan Das <sandipan.das@amd.com> wrote:
> >
> > Add events and metrics taken from the Processor Programming Reference
> > (PPR) for AMD Family 19h Model 11h Revision B1 processors which can be
> > found at: https://www.amd.com/system/files/TechDocs/55901_0.25.zip
> >
> > Previous versions can be found at:
> > v1: https://lore.kernel.org/all/20221207053007.336806-1-sandipan.das@amd.com/
> >
> > Changes in v2:
> > - Remove "bytes" from the names of data fabric bandwidth metrics which
> > use a scale unit.
> > - Use better group names for pipeline utilization metrics.
> > - Move patch that adds family-model mapping to the end of the series for
> > avoiding potential build issues.
> >
> > Sandipan Das (4):
> > perf vendor events amd: Add Zen 4 core events
> > perf vendor events amd: Add Zen 4 uncore events
> > perf vendor events amd: Add Zen 4 metrics
> > perf vendor events amd: Add Zen 4 mapping
>
> Series: Acked-by: Ian Rogers <irogers@google.com>
Please add the Acked-by: on a separate line, like
Series:
Acked-by: Ian Rogers <irogers@google.com>
To avoid confusing b4
Thanks,
- Arnaldo
> Thanks,
> Ian
>
> > .../pmu-events/arch/x86/amdzen4/branch.json | 82 ++
> > .../pmu-events/arch/x86/amdzen4/cache.json | 772 ++++++++++++
> > .../pmu-events/arch/x86/amdzen4/core.json | 122 ++
> > .../arch/x86/amdzen4/data-fabric.json | 1090 +++++++++++++++++
> > .../arch/x86/amdzen4/floating-point.json | 818 +++++++++++++
> > .../pmu-events/arch/x86/amdzen4/memory.json | 174 +++
> > .../pmu-events/arch/x86/amdzen4/other.json | 138 +++
> > .../pmu-events/arch/x86/amdzen4/pipeline.json | 98 ++
> > .../arch/x86/amdzen4/recommended.json | 334 +++++
> > tools/perf/pmu-events/arch/x86/mapfile.csv | 3 +-
> > 10 files changed, 3630 insertions(+), 1 deletion(-)
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/branch.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/cache.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/core.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/data-fabric.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/floating-point.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/memory.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/other.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/pipeline.json
> > create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/recommended.json
> >
> > --
> > 2.34.1
> >
--
- Arnaldo
prev parent reply other threads:[~2022-12-21 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 8:26 [PATCH v2 0/4] perf vendor events amd: Add Zen 4 events and metrics Sandipan Das
2022-12-14 8:26 ` [PATCH v2 1/4] perf vendor events amd: Add Zen 4 core events Sandipan Das
2022-12-14 8:26 ` [PATCH v2 2/4] perf vendor events amd: Add Zen 4 uncore events Sandipan Das
2022-12-14 8:26 ` [PATCH v2 3/4] perf vendor events amd: Add Zen 4 metrics Sandipan Das
2022-12-14 8:26 ` [PATCH v2 4/4] perf vendor events amd: Add Zen 4 mapping Sandipan Das
2022-12-14 15:59 ` [PATCH v2 0/4] perf vendor events amd: Add Zen 4 events and metrics Ian Rogers
2022-12-21 17:03 ` 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=Y6M8TeUR73AB+TKP@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jhladky@redhat.com \
--cc=jolsa@kernel.org \
--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=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=sandipan.das@amd.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).