From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: Shunsuke Nakamura <nakamura.shun@jp.fujitsu.com>,
<john.garry@huawei.com>
Cc: <mathieu.poirier@linaro.org>, <linux-kernel@vger.kernel.org>,
<leo.yan@linaro.org>, <will@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/3] perf vendor events: Add cache refill and DCZVA events
Date: Thu, 21 Jan 2021 19:39:20 +0800 [thread overview]
Message-ID: <b00bf252-e31f-b0eb-d0aa-0a62bcaee22e@hisilicon.com> (raw)
In-Reply-To: <20210121105425.2695843-2-nakamura.shun@jp.fujitsu.com>
Hi,
在 2021/1/21 18:54, Shunsuke Nakamura 写道:
> Adds L1 data cache refill prefetch, L2 data cache refill prefetch,
> and DCZVA instruction events.
A silly question, Does Arm define these events? I checked Arm ARM
document(DDI0487Fc) that these event numbers are reserved. Or maybe
I miss something.
Thanks,
Shaokun
>
> Signed-off-by: Shunsuke Nakamura <nakamura.shun@jp.fujitsu.com>
> ---
> .../perf/pmu-events/arch/arm64/armv8-recommended.json | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/tools/perf/pmu-events/arch/arm64/armv8-recommended.json b/tools/perf/pmu-events/arch/arm64/armv8-recommended.json
> index d0a1986..ee0e67d 100644
> --- a/tools/perf/pmu-events/arch/arm64/armv8-recommended.json
> +++ b/tools/perf/pmu-events/arch/arm64/armv8-recommended.json
> @@ -54,6 +54,12 @@
> "BriefDescription": "L1D cache invalidate"
> },
> {
> + "PublicDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch.",
> + "EventCode": "0x49",
> + "EventName": "L1D_CACHE_REFILL_PRF",
> + "BriefDescription": "This event counts L1D_CACHE_REFILL caused by software or hardware prefetch."
> + },
> + {
> "PublicDescription": "Attributable Level 1 data TLB refill, read",
> "EventCode": "0x4C",
> "EventName": "L1D_TLB_REFILL_RD",
> @@ -120,6 +126,12 @@
> "BriefDescription": "L2D cache invalidate"
> },
> {
> + "PublicDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch.",
> + "EventCode": "0x59",
> + "EventName": "L2D_CACHE_REFILL_PRF",
> + "BriefDescription": "This event counts L2D_CACHE_REFILL caused by software or hardware prefetch."
> + },
> + {
> "PublicDescription": "Attributable Level 2 data or unified TLB refill, read",
> "EventCode": "0x5c",
> "EventName": "L2D_TLB_REFILL_RD",
> @@ -408,6 +420,12 @@
> "BriefDescription": "Release consistency operation speculatively executed, Store-Release"
> },
> {
> + "PublicDescription": "This event counts architecturally executed zero blocking operations due to the 'DC ZVA' instruction.",
> + "EventCode": "0x9f",
> + "EventName": "DCZVA_SPEC",
> + "BriefDescription": "This event counts architecturally executed zero blocking operations due to the 'DC ZVA' instruction."
> + },
> + {
> "PublicDescription": "Attributable Level 3 data or unified cache access, read",
> "EventCode": "0xa0",
> "EventName": "L3D_CACHE_RD",
>
next prev parent reply other threads:[~2021-01-21 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 10:54 [PATCH v2 0/3] perf vendor events: Support PMU events for A64FX Shunsuke Nakamura
2021-01-21 10:54 ` [PATCH v2 1/3] perf vendor events: Add cache refill and DCZVA events Shunsuke Nakamura
2021-01-21 11:39 ` Shaokun Zhang [this message]
2021-01-21 17:43 ` John Garry
2021-01-22 8:35 ` nakamura.shun
2021-01-21 10:54 ` [PATCH v2 2/3] perf tools: Fix lexical definition of event name Shunsuke Nakamura
2021-01-21 10:54 ` [PATCH v2 3/3] perf vendor events: Add Fujitsu A64FX V1.2 pmu event Shunsuke Nakamura
2021-01-21 17:41 ` John Garry
2021-01-22 8:37 ` nakamura.shun
2021-01-25 12:46 ` John Garry
2021-01-26 8:03 ` nakamura.shun
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=b00bf252-e31f-b0eb-d0aa-0a62bcaee22e@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nakamura.shun@jp.fujitsu.com \
--cc=will@kernel.org \
/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®