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, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, adrian.hunter@intel.com, eranian@google.com,
ravi.bangoria@amd.com, ananth.narayan@amd.com
Subject: Re: [PATCH v2 0/4] perf vendor events amd: Add Zen 5 events and metrics
Date: Sat, 4 May 2024 15:12:02 -0300 [thread overview]
Message-ID: <ZjZ6csbnXZNUX1iY@x1> (raw)
In-Reply-To: <CAP-5=fVqr9E_YS-V=1rnrxH3AchRy8x0wR9wSpSwLiUNuMij=A@mail.gmail.com>
On Fri, May 03, 2024 at 09:29:27PM -0700, Ian Rogers wrote:
> On Fri, May 3, 2024 at 12:16 AM Sandipan Das <[1]sandipan.das@amd.com> wrote:
> Add events and metrics taken from the Performance Monitor Counters
> for
> AMD Family 1Ah Model 00h-0Fh Processors document available at
> [2]https://bugzilla.kernel.org/attachment.cgi?id=305974
<SNIP>
> Sandipan Das (4):
> perf vendor events amd: Add Zen 5 core events
> perf vendor events amd: Add Zen 5 uncore events
> perf vendor events amd: Add Zen 5 metrics
> perf vendor events amd: Add Zen 5 mapping
> Series:
> Reviewed-by: Ian Rogers <[4]irogers@google.com>
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2024-05-04 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 7:16 [PATCH v2 0/4] perf vendor events amd: Add Zen 5 events and metrics Sandipan Das
2024-05-03 7:16 ` [PATCH v2 1/4] perf vendor events amd: Add Zen 5 core events Sandipan Das
2024-05-03 7:16 ` [PATCH v2 2/4] perf vendor events amd: Add Zen 5 uncore events Sandipan Das
2024-05-03 7:16 ` [PATCH v2 3/4] perf vendor events amd: Add Zen 5 metrics Sandipan Das
2024-05-03 7:16 ` [PATCH v2 4/4] perf vendor events amd: Add Zen 5 mapping Sandipan Das
[not found] ` <CAP-5=fVqr9E_YS-V=1rnrxH3AchRy8x0wR9wSpSwLiUNuMij=A@mail.gmail.com>
2024-05-04 18:12 ` 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=ZjZ6csbnXZNUX1iY@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=eranian@google.com \
--cc=irogers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.