perf vendor events: Minor fixes to the README

Some grammatical fixes, and updates to some path references that have
since changed.

Signed-off-by: Kim Phillips <kim.phillips@amd.com>
Reviewed-by: Andi Kleen <ak@linux.intel.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Borislav Petkov <bp@suse.de>
Cc: Janakarajan Natarajan <janakarajan.natarajan@amd.com>
Cc: Jin Yao <yao.jin@linux.intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Kan Liang <kan.liang@linux.intel.com>
Cc: Luke Mujica <lukemujica@google.com>
Cc: Martin Liška <mliska@suse.cz>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: http://lore.kernel.org/lkml/20190919204306.12598-3-kim.phillips@amd.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
This commit is contained in:
Kim Phillips 2019-09-19 15:43:04 -05:00 committed by Arnaldo Carvalho de Melo
parent 0c03d3aa25
commit 93125562ce

View File

@ -30,9 +30,9 @@ the topic. Eg: "Floating-point.json".
All the topic JSON files for a CPU model/family should be in a separate All the topic JSON files for a CPU model/family should be in a separate
sub directory. Thus for the Silvermont X86 CPU: sub directory. Thus for the Silvermont X86 CPU:
$ ls tools/perf/pmu-events/arch/x86/Silvermont_core $ ls tools/perf/pmu-events/arch/x86/silvermont
Cache.json Memory.json Virtual-Memory.json cache.json memory.json virtual-memory.json
Frontend.json Pipeline.json frontend.json pipeline.json
The JSONs folder for a CPU model/family may be placed in the root arch 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 folder, or may be placed in a vendor sub-folder under the arch folder
@ -94,7 +94,7 @@ users to specify events by their name:
where 'pm_1plus_ppc_cmpl' is a Power8 PMU event. where 'pm_1plus_ppc_cmpl' is a Power8 PMU event.
However some errors in processing may cause the perf build to fail. However some errors in processing may cause the alias build to fail.
Mapfile format Mapfile format
=============== ===============
@ -119,7 +119,7 @@ where:
Header line Header line
The header line is the first line in the file, which is The header line is the first line in the file, which is
always _IGNORED_. It can empty. always _IGNORED_. It can be empty.
CPUID: CPUID:
CPUID is an arch-specific char string, that can be used CPUID is an arch-specific char string, that can be used
@ -138,15 +138,15 @@ where:
files, relative to the directory containing the mapfile.csv files, relative to the directory containing the mapfile.csv
Type: Type:
indicates whether the events or "core" or "uncore" events. indicates whether the events are "core" or "uncore" events.
Eg: Eg:
$ grep Silvermont tools/perf/pmu-events/arch/x86/mapfile.csv $ grep silvermont tools/perf/pmu-events/arch/x86/mapfile.csv
GenuineIntel-6-37,V13,Silvermont_core,core GenuineIntel-6-37,v13,silvermont,core
GenuineIntel-6-4D,V13,Silvermont_core,core GenuineIntel-6-4D,v13,silvermont,core
GenuineIntel-6-4C,V13,Silvermont_core,core GenuineIntel-6-4C,v13,silvermont,core
i.e the three CPU models use the JSON files (i.e PMU events) listed i.e the three CPU models use the JSON files (i.e PMU events) listed
in the directory 'tools/perf/pmu-events/arch/x86/Silvermont_core'. in the directory 'tools/perf/pmu-events/arch/x86/silvermont'.