Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: TPa7vrzCDDqqBfkxOj2vUbOfezpTAoI630ef2Van05BXBEtlL7GrLBnAwwATieh4DMG911w071
 UOBYGcpGzZMzT4vkH7AlrYBgvEIooWxaT5gzgS+hFwD/Alt39KL5iOAKiy7D+SGVePwPRnbyLP
 QrAUw9PHI+Asnh26jaYLvCBTkOal56wxALJOIxmIAiU1z4gk2bHrPpdDPm1J39Cce76W9CUP2g
 0YaYd6SOLB3UH+fr44d+N7xziIQcP2wqZ60zMMGO2SaW57L6uFST29zF7hrl0or+E59S1TS/DD
 YMU=
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-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
        "'linux-arm-kernel@lists.infradead.org'" 
        <linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v5 0/4] perf vendor events: Support PMU events for A64FX
Thread-Topic: [PATCH v5 0/4] perf vendor events: Support PMU events for A64FX
Thread-Index: AQHW+WMHTGeMdPN4T0+BYj0CxDS1qqpFEjAAgADvEKCAA3DPIIAEFEWQ
Date:   Mon, 8 Feb 2021 01:53:54 +0000
Message-ID: <OSBPR01MB4600E5D5B5BF038D5A3F8544F78F9@OSBPR01MB4600.jpnprd01.prod.outlook.com>
References: <20210202125140.1785583-1-nakamura.shun@jp.fujitsu.com>
 <57c6b89d-e0b2-3df4-8dcf-2cc71f772cb4@huawei.com>
 <OSBPR01MB4600991FC47D2E5A7E013F0CF7B49@OSBPR01MB4600.jpnprd01.prod.outlook.com>
 <OSBPR01MB46007C599F706F3C56B20E64F7B29@OSBPR01MB4600.jpnprd01.prod.outlook.com>
In-Reply-To: <OSBPR01MB46007C599F706F3C56B20E64F7B29@OSBPR01MB4600.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2ba54767-68b6-4363-9876-08d8cbd463f3
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Feb 2021 01:53:54.2439
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a19f121d-81e1-4858-a9d8-736e267fd4c7
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: mnHnDqYu7aYvY4rqQ+MZxxeDpyqUnfYlhHLZ5U/T480SiJte1S5HG3MSpQfDvoFfxKP1Ac5Ezq+iqoT4ymk5wcCwnWgQEOXsKK13TaxIFes=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS3PR01MB5751
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi, John

> > > Apart from that, I think that we're a bit uncertain about patch 3/4
> > What are your concerns?
> > I think it's okay for perf to read a new event code with a number at th=
e
> beginning.
>=20
> The impact of this fix is on {name} and later rules.
> parse_events.l uses {name} only in one place.
> The only rule defined after {name} is {name_tag}.
>=20
> I think the point of current fix is that the rules defined after {name} a=
re not
> misrecognize and the syntax is not broken.
> {name_tag} starts with ', but {name} does not contain'.
> Therefore, the corrected {name} does not misrecognize the {name_tag}, and=
 I
> think there is no problem.
Do you have any advice?

Best Regards
Shunsuke