2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
The contents of this directory allow users to specify PMU events in their
|
|
|
|
CPUs by their symbolic names rather than raw event codes (see example below).
|
|
|
|
|
|
|
|
The main program in this directory, is the 'jevents', which is built and
|
|
|
|
executed _BEFORE_ the perf binary itself is built.
|
|
|
|
|
|
|
|
The 'jevents' program tries to locate and process JSON files in the directory
|
|
|
|
tree tools/perf/pmu-events/arch/foo.
|
|
|
|
|
|
|
|
- Regular files with '.json' extension in the name are assumed to be
|
|
|
|
JSON files, each of which describes a set of PMU events.
|
|
|
|
|
2018-03-08 18:58:26 +08:00
|
|
|
- The CSV file that maps a specific CPU to its set of PMU events is to
|
|
|
|
be named 'mapfile.csv' (see below for mapfile format).
|
2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
- Directories are traversed, but all other files are ignored.
|
|
|
|
|
perf vendor events: Add support for arch standard events
For some architectures (like arm), there are architecture- defined
events. Sometimes these events may be "recommended" according to the
architecture standard, in that the implementer is free ignore the
"recommendation" and create its custom event.
This patch adds support for parsing standard events from arch-defined
JSONs, and fixing up vendor events when they have implemented these
events as standard.
Support is also ensured that the vendor may implement their own custom
events.
A new step is added to the pmu events parsing to fix up the vendor
events with the arch-standard events.
The arch-defined JSONs must be placed in the arch root folder for
preprocessing prior to tree JSON processing.
In the vendor JSON, to specify that the arch event is supported, the
keyword "ArchStdEvent" should be used, like this:
[
{
"ArchStdEvent": "L1D_CACHE_WR",
},
]
Matching is based on the "EventName" field in the architecture JSON.
No other JSON objects are strictly required. However, for other objects
added, these take precedence over architecture defined standard events,
thus supporting separate events which have the same event code.
Signed-off-by: John Garry <john.garry@huawei.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: William Cohen <wcohen@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linuxarm@huawei.com
Link: http://lkml.kernel.org/r/1520506716-197429-8-git-send-email-john.garry@huawei.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-03-08 18:58:32 +08:00
|
|
|
- To reduce JSON event duplication per architecture, platform JSONs may
|
|
|
|
use "ArchStdEvent" keyword to dereference an "Architecture standard
|
|
|
|
events", defined in architecture standard JSONs.
|
|
|
|
Architecture standard JSONs must be located in the architecture root
|
|
|
|
folder. Matching is based on the "EventName" field.
|
|
|
|
|
2016-09-16 06:24:52 +08:00
|
|
|
The PMU events supported by a CPU model are expected to grouped into topics
|
|
|
|
such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
|
|
|
|
should be placed in a separate JSON file - where the file name identifies
|
|
|
|
the topic. Eg: "Floating-point.json".
|
|
|
|
|
|
|
|
All the topic JSON files for a CPU model/family should be in a separate
|
|
|
|
sub directory. Thus for the Silvermont X86 CPU:
|
|
|
|
|
2019-09-20 04:43:04 +08:00
|
|
|
$ ls tools/perf/pmu-events/arch/x86/silvermont
|
|
|
|
cache.json memory.json virtual-memory.json
|
|
|
|
frontend.json pipeline.json
|
2016-09-16 06:24:52 +08:00
|
|
|
|
perf vendor events: Add support for pmu events vendor subdirectory
For some architectures (like arm), it is required to support a vendor
subdirectory and not locate all the JSONs for a specific vendor in the
same folder.
This is because all the events for the same vendor will be placed in the
same pmu events table, which may cause conflict. This conflict would be
in the instance that a vendor's custom implemented events do have the
same meaning on different platforms, so events in the pmu table would
conflict. In addition, per list command may show events which are not
even supported for a given platform.
This patch adds support for a arch/vendor/platform directory hierarchy,
while maintaining backwards-compatibility for existing arch/platform
structure. In this, each platform would always have its own pmu events
table.
In generated file pmu_events.c, each platform table name is in the
format pme{_vendor}_platform, like this:
struct pmu_events_map pmu_events_map[] = {
{
.cpuid = "0x00000000420f5160",
.version = "v1",
.type = "core",
.table = pme_cavium_thunderx2
},
{
.cpuid = 0,
.version = 0,
.type = 0,
.table = 0,
},
};
Signed-off-by: John Garry <john.garry@huawei.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Tested-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Will Deacon <will.deacon@arm.com>
Cc: William Cohen <wcohen@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linuxarm@huawei.com
Link: http://lkml.kernel.org/r/1520506716-197429-5-git-send-email-john.garry@huawei.com
Link: http://lkml.kernel.org/r/1521047452-28565-1-git-send-email-john.garry@huawei.com
[ Add missing limits.h include, fixing the build on at least all Alpine Linux versions tested (3.4 to 3.7 + edge), ]
[ Applied a patch to fix reading ./.. directories in XFS, see second Link tag ]
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2018-03-08 18:58:29 +08:00
|
|
|
The JSONs folder for a CPU model/family may be placed in the root arch
|
|
|
|
folder, or may be placed in a vendor sub-folder under the arch folder
|
|
|
|
for instances where the arch and vendor are not the same.
|
|
|
|
|
2016-09-16 06:24:52 +08:00
|
|
|
Using the JSON files and the mapfile, 'jevents' generates the C source file,
|
|
|
|
'pmu-events.c', which encodes the two sets of tables:
|
|
|
|
|
|
|
|
- Set of 'PMU events tables' for all known CPUs in the architecture,
|
|
|
|
(one table like the following, per JSON file; table name 'pme_power8'
|
|
|
|
is derived from JSON file name, 'power8.json').
|
|
|
|
|
|
|
|
struct pmu_event pme_power8[] = {
|
|
|
|
|
|
|
|
...
|
|
|
|
|
|
|
|
{
|
|
|
|
.name = "pm_1plus_ppc_cmpl",
|
|
|
|
.event = "event=0x100f2",
|
|
|
|
.desc = "1 or more ppc insts finished,",
|
|
|
|
},
|
|
|
|
|
|
|
|
...
|
|
|
|
}
|
|
|
|
|
|
|
|
- A 'mapping table' that maps each CPU of the architecture, to its
|
|
|
|
'PMU events table'
|
|
|
|
|
|
|
|
struct pmu_events_map pmu_events_map[] = {
|
|
|
|
{
|
|
|
|
.cpuid = "004b0000",
|
|
|
|
.version = "1",
|
|
|
|
.type = "core",
|
|
|
|
.table = pme_power8
|
|
|
|
},
|
|
|
|
...
|
|
|
|
|
|
|
|
};
|
|
|
|
|
|
|
|
After the 'pmu-events.c' is generated, it is compiled and the resulting
|
|
|
|
'pmu-events.o' is added to 'libperf.a' which is then used to build perf.
|
|
|
|
|
|
|
|
NOTES:
|
|
|
|
1. Several CPUs can support same set of events and hence use a common
|
|
|
|
JSON file. Hence several entries in the pmu_events_map[] could map
|
|
|
|
to a single 'PMU events table'.
|
|
|
|
|
|
|
|
2. The 'pmu-events.h' has an extern declaration for the mapping table
|
|
|
|
and the generated 'pmu-events.c' defines this table.
|
|
|
|
|
|
|
|
3. _All_ known CPU tables for architecture are included in the perf
|
|
|
|
binary.
|
|
|
|
|
|
|
|
At run time, perf determines the actual CPU it is running on, finds the
|
|
|
|
matching events table and builds aliases for those events. This allows
|
|
|
|
users to specify events by their name:
|
|
|
|
|
|
|
|
$ perf stat -e pm_1plus_ppc_cmpl sleep 1
|
|
|
|
|
|
|
|
where 'pm_1plus_ppc_cmpl' is a Power8 PMU event.
|
|
|
|
|
2019-09-20 04:43:04 +08:00
|
|
|
However some errors in processing may cause the alias build to fail.
|
2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
Mapfile format
|
|
|
|
===============
|
|
|
|
|
|
|
|
The mapfile enables multiple CPU models to share a single set of PMU events.
|
|
|
|
It is required even if such mapping is 1:1.
|
|
|
|
|
|
|
|
The mapfile.csv format is expected to be:
|
|
|
|
|
|
|
|
Header line
|
|
|
|
CPUID,Version,Dir/path/name,Type
|
|
|
|
|
|
|
|
where:
|
|
|
|
|
|
|
|
Comma:
|
|
|
|
is the required field delimiter (i.e other fields cannot
|
|
|
|
have commas within them).
|
|
|
|
|
|
|
|
Comments:
|
|
|
|
Lines in which the first character is either '\n' or '#'
|
|
|
|
are ignored.
|
|
|
|
|
|
|
|
Header line
|
|
|
|
The header line is the first line in the file, which is
|
2019-09-20 04:43:04 +08:00
|
|
|
always _IGNORED_. It can be empty.
|
2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
CPUID:
|
|
|
|
CPUID is an arch-specific char string, that can be used
|
|
|
|
to identify CPU (and associate it with a set of PMU events
|
|
|
|
it supports). Multiple CPUIDS can point to the same
|
|
|
|
File/path/name.json.
|
|
|
|
|
|
|
|
Example:
|
|
|
|
CPUID == 'GenuineIntel-6-2E' (on x86).
|
|
|
|
CPUID == '004b0100' (PVR value in Powerpc)
|
|
|
|
Version:
|
|
|
|
is the Version of the mapfile.
|
|
|
|
|
|
|
|
Dir/path/name:
|
|
|
|
is the pathname to the directory containing the CPU's JSON
|
|
|
|
files, relative to the directory containing the mapfile.csv
|
|
|
|
|
|
|
|
Type:
|
2019-09-20 04:43:04 +08:00
|
|
|
indicates whether the events are "core" or "uncore" events.
|
2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
|
|
|
|
Eg:
|
|
|
|
|
2019-09-20 04:43:04 +08:00
|
|
|
$ grep silvermont tools/perf/pmu-events/arch/x86/mapfile.csv
|
|
|
|
GenuineIntel-6-37,v13,silvermont,core
|
|
|
|
GenuineIntel-6-4D,v13,silvermont,core
|
|
|
|
GenuineIntel-6-4C,v13,silvermont,core
|
2016-09-16 06:24:52 +08:00
|
|
|
|
|
|
|
i.e the three CPU models use the JSON files (i.e PMU events) listed
|
2019-09-20 04:43:04 +08:00
|
|
|
in the directory 'tools/perf/pmu-events/arch/x86/silvermont'.
|