From: "Liang, Kan" <kan.liang@linux.intel.com>
To: zhengjun.xing@linux.intel.com, acme@kernel.org,
peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@intel.com, jolsa@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
irogers@google.com, adrian.hunter@intel.com, ak@linux.intel.com
Subject: Re: [PATCH 2/2] perf vendor events intel: Update event list for Snowridgex
Date: Wed, 8 Jun 2022 08:49:45 -0400 [thread overview]
Message-ID: <59b85c65-198c-5147-bbc6-818ce2234b6c@linux.intel.com> (raw)
In-Reply-To: <20220608063439.1997394-2-zhengjun.xing@linux.intel.com>
On 6/8/2022 2:34 AM, zhengjun.xing@linux.intel.com wrote:
> {
> - "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
> + "BriefDescription": "All DRAM write CAS commands issued",
> "Counter": "0,1,2,3",
> "CounterType": "PGMABLE",
> "EventCode": "0x04",
> - "EventName": "LLC_MISSES.MEM_WRITE",
The old convertor tool creates many alias to replace the event in the
event list. The LLC_MISSES.MEM_WRITE event is one of them.
There is no problem to add the original event name. But I think we
should keep both alias and the original name, in case someone already
used the alias in their script.
> + "EventName": "UNC_M_CAS_COUNT.WR",
> "PerPkg": "1",
> - "ScaleUnit": "64Bytes",
> "UMask": "0x30",
> "Unit": "iMC"
> },
Thanks,
Kan
prev parent reply other threads:[~2022-06-08 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:34 [PATCH 1/2] perf vendor events intel: Rename tremontx to snowridgex zhengjun.xing
2022-06-08 6:34 ` [PATCH 2/2] perf vendor events intel: Update event list for Snowridgex zhengjun.xing
2022-06-08 12:49 ` Liang, Kan [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=59b85c65-198c-5147-bbc6-818ce2234b6c@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=zhengjun.xing@linux.intel.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®