#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.