Lines Matching full:events

2 The contents of this directory allow users to specify PMU events in their
9 tree tools/perf/pmu-events/arch/foo.
12 	  JSON files, each of which describes a set of PMU events.
14 	- The CSV file that maps a specific CPU to its set of PMU events is to
21 	  events", defined in architecture standard JSONs.
25 The PMU events supported by a CPU model are expected to grouped into topics
26 such as Pipelining, Cache, Memory, Floating-point etc. All events for a topic
33 	$ ls tools/perf/pmu-events/arch/x86/silvermont
42 'pmu-events.c', which encodes the two sets of tables:
44 	- Set of 'PMU events tables' for all known CPUs in the architecture,
62 	  'PMU events table'
75 After the 'pmu-events.c' is generated, it is compiled and the resulting
76 'pmu-events.o' is added to 'libperf.a' which is then used to build perf.
79 	1. Several CPUs can support same set of events and hence use a common
81 	   to a single 'PMU events table'.
83 	2. The 'pmu-events.h' has an extern declaration for the mapping table
84 	   and the generated 'pmu-events.c' defines this table.
90 matching events table and builds aliases for those events. This allows
91 users to specify events by their name:
102 The mapfile enables multiple CPU models to share a single set of PMU events.
126 		to identify CPU (and associate it with a set of PMU events
141 		indicates whether the events are "core" or "uncore" events.
146 	$ grep silvermont tools/perf/pmu-events/arch/x86/mapfile.csv
151 	i.e the three CPU models use the JSON files (i.e PMU events) listed
152 	in the directory 'tools/perf/pmu-events/arch/x86/silvermont'.