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: eBeE8fCp5mTVw2GT/fOfU4Ji8FHLZ/sA/8zYMfd6wukgF7j9+jNNSvKn6rtB8jiK9a4iYLClNF
 cM8UveL6b3XDijKeUs1r+/zTfwS5WFWHdGINDLvNL6WRcNwdhom8O4Dojdwd/g6nl22yPo47Ev
 o7p/2vOJyhXsGUdL06mGg+DuxFzyF/zSQP53KiiAAcRRxx8CePyx6hWwuvKwb3hW/TnU/w9jw1
 D51AB2a6rmlTg8574UyHlIxeSsJTXsFqApYkNbhSUBGQdE7BzAku1xb4pcISthv1Bu9r8VUnIF
 O54=
From:   "nakamura.shun@fujitsu.com" <nakamura.shun@fujitsu.com>
To:     Jiri Olsa <jolsa@redhat.com>
CC:     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>,
        "namhyung@kernel.org" <namhyung@kernel.org>,
        "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 v7 2/4] perf tools: Add lexical definition of event name
Thread-Topic: [PATCH v7 2/4] perf tools: Add lexical definition of event name
Thread-Index: AQHXEKlBkVxBxv6w0EWmceCNSxz1JapzkeUAgAGbKNqAAitpgIACFK2X
Date:   Mon, 8 Mar 2021 03:19:43 +0000
Message-ID: <OSBPR01MB46006C7AB7B1096DD2E1904DF7939@OSBPR01MB4600.jpnprd01.prod.outlook.com>
References: <20210304032610.3112996-1-nakamura.shun@fujitsu.com>
 <20210304032610.3112996-3-nakamura.shun@fujitsu.com>
 <74955041-45ab-10df-e044-5d64898c81d9@huawei.com>
 <OSBPR01MB4600C6910F2AFFC5819C8145F7969@OSBPR01MB4600.jpnprd01.prod.outlook.com>,<YEPUhZPoUZrzGvaJ@krava>
In-Reply-To: <YEPUhZPoUZrzGvaJ@krava>
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: c7703106-2074-4756-1c3d-08d8e1e104c9
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2021 03:19:43.6295
 (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: KRg7aIVZnmLImnuE2+2mItIF6ADBwdf6E/ZTO2Zx1sFu3QEcGJAaeTG3ozo6byEP0CmXkyUFbDYKTVyX6WF7f5etz/fv+VTV/k0QXWxaWLc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS3PR01MB5751
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi, jirka=0A=
=0A=
> > > > From: Shunsuke Nakamura <nakamura.shun@jp.fujitsu.com>=0A=
> > > > =0A=
> > > > Add the lexical definition of event name so that the numbers are re=
cognizable.=0A=
> > > > =0A=
> > > =0A=
> > > Sorry for the hassle, but it's not clear that we got a definitive =0A=
> > > conclusion on this patch from v6 series:=0A=
> > > =0A=
> > > https://lore.kernel.org/lkml/YCuo01Wxxe%2FMCrC5@krava/=0A=
> > > =0A=
> > > Would it be so much worse for you to change format of these event nam=
es =0A=
> > > to not start with a numberic?=0A=
> > I was trying to match the specifications published by Fujitsu exactly.=
=0A=
> > We also thought that being able to parse event names starting with a nu=
mber would be an improvement for perf.=0A=
> > We've discussed it with the team, but we decided to change the event na=
me.=0A=
> =0A=
> hum, I'm not sure what's the final decision in here.. are you keeping=0A=
> numbers in the start? would be much easier if you did not ;-)=0A=
I don't keep the event name starting with a number.=0A=
=0A=
v8 patch serase changed the event name starting with a number to start with=
 "_".=0A=
https://lore.kernel.org/linux-arm-kernel/20210305101841.3133721-1-nakamura.=
shun@fujitsu.com/=0A=
=0A=
Best Regards=0A=
Shunsuke=0A=
=0A=