[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f698b4dc-be65-9911-9dee-6f2534c0ab83@huawei.com>
Date: Thu, 19 Oct 2017 11:29:04 +0100
From: John Garry <john.garry@...wei.com>
To: Ganapatrao Kulkarni <gklkml16@...il.com>
CC: Will Deacon <will.deacon@....com>,
Shaokun Zhang <zhangshaokun@...ilicon.com>,
Ganapatrao Kulkarni <ganapatrao.kulkarni@...ium.com>,
<linux-kernel@...r.kernel.org>, Linuxarm <linuxarm@...wei.com>,
<jonathan.cameron@...wei.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
"Arnaldo Carvalho de Melo" <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Subject: Re: [PATCH] perf vendor events arm64: Add hip08 implementation
defined PMU core events
>>
>> #Family-model,Version,Filename,EventType
>> 0x00000000420f5160,v1,cavium,core
>> 0x00000000420f5161,v1,cavium,core
>
> certainly, there is Part number(PartNum, bits [15:4] ) change from
> thunderx2 to thunderx3.
> thunderx3 should have its own json file describing all its supported events.
> same applies to other SoCs as well.
>
> IIUC, the idea of ignoring Revision and Variants is that, the PMU
> design/version wont change across Revisions and Variants.
>
Hi Ganapatrao,
Right, I should have modified the part num for my illustration, but I am
still concerned. Please see my example in the other mail and check what
I am missing.
Thanks,
John
Powered by blists - more mailing lists