From: John Garry <john.garry@huawei.com>
To: Shunsuke Nakamura <nakamura.shun@jp.fujitsu.com>,
<will@kernel.org>, <mathieu.poirier@linaro.org>,
<leo.yan@linaro.org>, <peterz@infradead.org>, <mingo@redhat.com>,
<acme@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
<namhyung@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <nakamura.shun@fujitsu.com>
Subject: Re: [PATCH v4 2/4] perf vendor events: Add L2I_TLB, SVE, SIMD, and FP events
Date: Mon, 1 Feb 2021 14:22:38 +0000 [thread overview]
Message-ID: <fd65e539-d8cf-e1d0-103b-ad8154a42173@huawei.com> (raw)
In-Reply-To: <20210201111310.3231469-3-nakamura.shun@jp.fujitsu.com>
On 01/02/2021 11:13, Shunsuke Nakamura wrote:
I think that you will need to fix the subject, like:
perf vendor events arm64: Add more common and uarch events
> Add the following events.
It would be good to mention your reference document.
>
> Common architectural events:
> - L2I_TLB_REFILL
> - L2I_TLB
> - SIMD_INST_RETIRED
> - SVE_INST_RETIRED
>
> Common microarchitectural events:
> - UOP_SPEC
> - SVE_MATH_SPEC
> - FP_SPEC
> - FP_FMA_SPEC
> - FP_RECPE_SPEC
> - FP_CVT_SPEC
> - ASE_SVE_INT_SPEC
> - SVE_PRED_SPEC
> - SVE_MOVPRFX_SPEC
> - SVE_MOVPRFX_U_SPEC
> - ASE_SVE_LD_SPEC
> - ASE_SVE_ST_SPEC
> - PRF_SPEC
> - BASE_LD_REG_SPEC
> - BASE_ST_REG_SPEC
> - SVE_LDR_REG_SPEC
> - SVE_STR_REG_SPEC
> - SVE_LDR_PREG_SPEC
> - SVE_STR_PREG_SPEC
> - SVE_PRF_CONTIG_SPEC
> - ASE_SVE_LD_MULTI_SPEC
> - ASE_SVE_ST_MULTI_SPEC
> - SVE_LD_GATHER_SPEC
> - SVE_ST_SCATTER_SPEC
> - SVE_PRF_GATHER_SPEC
> - SVE_LDFF_SPEC
> - FP_SCALE_OPS_SPEC
> - FP_FIXED_OPS_SPEC
> - FP_HP_SCALE_OPS_SPEC
> - FP_HP_FIXED_OPS_SPEC
> - FP_SP_SCALE_OPS_SPEC
> - FP_SP_FIXED_OPS_SPEC
> - FP_DP_SCALE_OPS_SPEC
> - FP_DP_FIXED_OPS_SPEC
>
> Signed-off-by: Shunsuke Nakamura<nakamura.shun@fujitsu.com>
Apart from those, above:
Reviewed-by: John Garry <john.garry@huawei.com>
next prev parent reply other threads:[~2021-02-01 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 11:13 [PATCH v4 0/4] perf vendor events: Support PMU events for A64FX Shunsuke Nakamura
2021-02-01 11:13 ` [PATCH v4 1/4] perf vendor events arm64: Add common and uarch event JSON Shunsuke Nakamura
2021-02-01 11:13 ` [PATCH v4 2/4] perf vendor events: Add L2I_TLB, SVE, SIMD, and FP events Shunsuke Nakamura
2021-02-01 14:22 ` John Garry [this message]
2021-02-02 9:53 ` nakamura.shun
2021-02-02 10:58 ` nakamura.shun
2021-02-01 11:13 ` [PATCH v4 3/4] perf tools: Fix lexical definition of event name Shunsuke Nakamura
2021-02-01 14:33 ` John Garry
2021-02-02 9:56 ` nakamura.shun
2021-02-02 11:03 ` nakamura.shun
2021-02-01 11:13 ` [PATCH v4 4/4] perf vendor events: Add Fujitsu A64FX V1.2 pmu event Shunsuke Nakamura
2021-02-01 14:29 ` John Garry
2021-02-02 9:59 ` nakamura.shun
2021-02-02 11:09 ` 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=fd65e539-d8cf-e1d0-103b-ad8154a42173@huawei.com \
--to=john.garry@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=nakamura.shun@fujitsu.com \
--cc=nakamura.shun@jp.fujitsu.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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®