From: "nakamura.shun@fujitsu.com" <nakamura.shun@fujitsu.com>
To: 'John Garry' <john.garry@huawei.com>,
"will@kernel.org" <will@kernel.org>,
"mathieu.poirier@linaro.org" <mathieu.poirier@linaro.org>,
"leo.yan@linaro.org" <leo.yan@linaro.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"namhyung@kernel.org" <namhyung@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v4 3/4] perf tools: Fix lexical definition of event name
Date: Tue, 2 Feb 2021 09:56:18 +0000 [thread overview]
Message-ID: <OSBPR01MB4600CF896542C021AACFD574F7B59@OSBPR01MB4600.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <b25fe15e-f27b-fdb1-41ce-9728ce78d52b@huawei.com>
Hi, John
I have applied this patch and confirmed that the event can be specified correctly.
Event names are defined in the A64FX specification.
I want to deal with it at that time if there is a problem.
So I would like to resend the v5 patch and wait for advice from others.
Best Regards
Shunsuke
next prev parent reply other threads:[~2021-02-02 10:07 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
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 [this message]
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=OSBPR01MB4600CF896542C021AACFD574F7B59@OSBPR01MB4600.jpnprd01.prod.outlook.com \
--to=nakamura.shun@fujitsu.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=john.garry@huawei.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=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®