From: Sandipan Das <sandipan.das@amd.com>
To: Ian Rogers <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@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 0/4] perf vendor events amd: Add Zen 4 events and metrics
Date: Wed, 7 Dec 2022 12:23:14 +0530 [thread overview]
Message-ID: <e490cd35-aece-25b5-de96-b2f64f6a9b94@amd.com> (raw)
In-Reply-To: <CAP-5=fWhqWfwTwnh5SWiLamXkuZbMnefASxkLByH6a44kdc5Bg@mail.gmail.com>
On 12/7/2022 11:36 AM, Ian Rogers wrote:
> On Tue, Dec 6, 2022 at 9:30 PM 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>>>
>> Sandipan Das (4):
>> perf vendor events amd: Add Zen 4 mapping
>
> Adding the mapping first may break the build until the core events are added.
>
Agreed. Will fix this in the next version.
- Sandipan
prev parent reply other threads:[~2022-12-07 6:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 5:30 Sandipan Das
2022-12-07 5:30 ` [PATCH 1/4] perf vendor events amd: Add Zen 4 mapping Sandipan Das
2022-12-07 5:30 ` [PATCH 2/4] perf vendor events amd: Add Zen 4 core events Sandipan Das
2022-12-07 5:30 ` [PATCH 3/4] perf vendor events amd: Add Zen 4 uncore events Sandipan Das
2022-12-07 5:30 ` [PATCH 4/4] perf vendor events amd: Add Zen 4 metrics Sandipan Das
2022-12-07 6:05 ` Ian Rogers
2022-12-07 6:58 ` Sandipan Das
2022-12-07 17:35 ` Ian Rogers
2022-12-07 17:44 ` Ian Rogers
2022-12-13 9:45 ` Sandipan Das
2022-12-07 6:06 ` [PATCH 0/4] perf vendor events amd: Add Zen 4 events and metrics Ian Rogers
2022-12-07 6:53 ` Sandipan Das [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=e490cd35-aece-25b5-de96-b2f64f6a9b94@amd.com \
--to=sandipan.das@amd.com \
--cc=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 \
/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
all inboxes | Powered by JetHome®