perf/core improvements and fixes
Arnaldo Carvalho de Melo
maintainerHi Ingo,
Please consider pulling,
- Arnaldo
Test results at the end of this message, as usual.
The following changes since commit 631fe154edb0a37308d0116a0f9b7bba9dca6218:
perf/x86: Update rdpmc_always_available static key to the modern API (2018-03-27 07:53:00 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.17-20180328
for you to fetch changes up to 109d59b900e78834c66657dd4748fcedb9a1fe8d:
perf vendor events s390: Add JSON files for IBM z14 (2018-03-27 13:13:39 -0300)
----------------------------------------------------------------
perf/core improvements and fixes:
- Be consistent when checking if a perf_mmap instance had its ring buffer unmmaped, fixing segfaults noticed in 'perf trace' (Kan Liang, Arnaldo Carvalho de Melo)
- Avoid adding the same option multiple times to the 'diff' command in check-headers.sh (Jiri Olsa)
- Add vendor event files (JSON format) to various IBM s390 models (z10EC, z10BC, z196, zEC12, zBC12, z13 and z14) (Thomas Richter)
----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
perf mmap: Be consistent when checking for an unmaped ring buffer
Jiri Olsa (1):
perf build: Fix check-headers.sh opts assignment
Kan Liang (1):
perf mmap: Fix accessing unmapped mmap in perf_mmap__read_done()
Thomas Richter (5):
perf vendor events s390: Add JSON files for IBM z10EC z10BC perf vendor events s390: Add JSON files for IBM z196 perf vendor events s390: Add JSON files for IBM zEC12 zBC12 perf vendor events s390: Add JSON files for IBM z13 perf vendor events s390: Add JSON files for IBM z14
tools/perf/check-headers.sh | 1 + tools/perf/pmu-events/arch/s390/cf_z10/basic.json | 74 +++++ tools/perf/pmu-events/arch/s390/cf_z10/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z10/extended.json | 110 +++++++ tools/perf/pmu-events/arch/s390/cf_z13/basic.json | 74 +++++ tools/perf/pmu-events/arch/s390/cf_z13/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z13/extended.json | 338 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/cf_z14/basic.json | 50 +++ tools/perf/pmu-events/arch/s390/cf_z14/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z14/extended.json | 320 +++++++++++++++++++ tools/perf/pmu-events/arch/s390/cf_z196/basic.json | 74 +++++ .../perf/pmu-events/arch/s390/cf_z196/crypto.json | 98 ++++++ .../pmu-events/arch/s390/cf_z196/extended.json | 146 +++++++++ .../perf/pmu-events/arch/s390/cf_zec12/basic.json | 74 +++++ .../perf/pmu-events/arch/s390/cf_zec12/crypto.json | 98 ++++++ .../pmu-events/arch/s390/cf_zec12/extended.json | 212 +++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 6 + tools/perf/util/mmap.c | 19 +- 18 files changed, 1987 insertions(+), 1 deletion(-) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/mapfile.csv
Test results:
The first ones are container (docker) based builds of tools/perf with and without libelf support. Where clang is available, it is also used to build perf with/without libelf.
The objtool and samples/bpf/ builds are disabled now that I'm switching from using the sources in a local volume to fetching them from a http server to build it inside the container, to make it easier to build in a container cluster. Those will come back later.
Several are cross builds, the ones with -x-ARCH and the android one, and those may not have all the features built, due to lack of multi-arch devel packages, available and being used so far on just a few, like debian:experimental-x-{arm64,mipsel}.
The 'perf test' one will perform a variety of tests exercising tools/perf/util/, tools/lib/{bpf,traceevent,etc}, as well as run perf commands with a variety of command line event specifications to then intercept the sys_perf_event syscall to check that the perf_event_attr fields are set up as expected, among a variety of other unit tests.
Then there is the 'make -C tools/perf build-test' ones, that build tools/perf/ with a variety of feature sets, exercising the build with an incomplete set of features as well as with a complete one. It is planned to have it run on each of the containers mentioned above, using some container orchestration infrastructure. Get in contact if interested in helping having this in place.
# docker images | grep none # time dm 1 alpine:3.4 : Ok gcc (Alpine 5.3.0) 5.3.0 2 alpine:3.5 : Ok gcc (Alpine 6.2.1) 6.2.1 20160822 3 alpine:3.6 : Ok gcc (Alpine 6.3.0) 6.3.0 4 alpine:3.7 : Ok gcc (Alpine 6.4.0) 6.4.0 5 alpine:edge : Ok gcc (Alpine 6.4.0) 6.4.0 6 amazonlinux:1 : Ok gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11) 7 amazonlinux:2 : Ok gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2) 8 android-ndk:r12b-arm : Ok arm-linux-androideabi-gcc (GCC) 4.9.x 20150123 (prerelease) 9 android-ndk:r15c-arm : Ok arm-linux-androideabi-gcc (GCC) 4.9.x 20150123 (prerelease) 10 centos:5 : Ok gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55) 11 centos:6 : Ok gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18) 12 centos:7 : Ok gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16) 13 debian:7 : Ok gcc (Debian 4.7.2-5) 4.7.2 14 debian:8 : Ok gcc (Debian 4.9.2-10+deb8u1) 4.9.2 15 debian:9 : Ok gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516 16 debian:experimental : Ok gcc (Debian 7.3.0-12) 7.3.0 17 debian:experimental-x-arm64 : Ok aarch64-linux-gnu-gcc (Debian 7.3.0-12) 7.3.0 18 debian:experimental-x-mips : Ok mips-linux-gnu-gcc (Debian 7.3.0-12) 7.3.0 19 debian:experimental-x-mips64 : Ok mips64-linux-gnuabi64-gcc (Debian 7.3.0-11) 7.3.0 20 debian:experimental-x-mipsel : Ok mipsel-linux-gnu-gcc (Debian 7.3.0-12) 7.3.0 21 fedora:20 : Ok gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-7) 22 fedora:21 : Ok gcc (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) 23 fedora:22 : Ok gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) 24 fedora:23 : Ok gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6) 25 fedora:24 : Ok gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1) 26 fedora:24-x-ARC-uClibc : Ok arc-linux-gcc (ARCompact ISA Linux uClibc toolchain 2017.09-rc2) 7.1.1 20170710 27 fedora:25 : Ok gcc (GCC) 6.4.1 20170727 (Red Hat 6.4.1-1) 28 fedora:26 : Ok gcc (GCC) 7.3.1 20180130 (Red Hat 7.3.1-2) 29 fedora:27 : Ok gcc (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5) 30 fedora:rawhide : Ok gcc (GCC) 8.0.1 20180222 (Red Hat 8.0.1-0.16) 31 gentoo-stage3-amd64:latest : Ok gcc (Gentoo 6.4.0-r1 p1.3) 6.4.0 32 mageia:5 : Ok gcc (GCC) 4.9.2 33 mageia:6 : Ok gcc (Mageia 5.5.0-1.mga6) 5.5.0 34 opensuse:42.1 : Ok gcc (SUSE Linux) 4.8.5 35 opensuse:42.2 : Ok gcc (SUSE Linux) 4.8.5 36 opensuse:42.3 : Ok gcc (SUSE Linux) 4.8.5 37 opensuse:tumbleweed : Ok gcc (SUSE Linux) 7.3.0 38 oraclelinux:6 : Ok gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18) 39 oraclelinux:7 : Ok gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16.0.3) 40 ubuntu:12.04.5 : Ok gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 41 ubuntu:14.04.4 : Ok gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 42 ubuntu:14.04.4-x-linaro-arm64 : Ok aarch64-linux-gnu-gcc (Linaro GCC 5.4-2017.05) 5.4.1 20170404 43 ubuntu:15.04 : Ok gcc (Ubuntu 4.9.2-10ubuntu13) 4.9.2 44 ubuntu:16.04 : Ok gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 45 ubuntu:16.04-x-arm : Ok arm-linux-gnueabihf-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 46 ubuntu:16.04-x-arm64 : Ok aarch64-linux-gnu-gcc (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 47 ubuntu:16.04-x-powerpc : Ok powerpc-linux-gnu-gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 48 ubuntu:16.04-x-powerpc64 : Ok powerpc64-linux-gnu-gcc (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 49 ubuntu:16.04-x-powerpc64el : Ok powerpc64le-linux-gnu-gcc (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 50 ubuntu:16.04-x-s390 : Ok s390x-linux-gnu-gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609 51 ubuntu:16.10 : Ok gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005 52 ubuntu:17.04 : Ok gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406 53 ubuntu:17.10 : Ok gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0 54 ubuntu:18.04 : Ok gcc (Ubuntu 7.2.0-16ubuntu1) 7.2.0 #
# uname -r 4.16.0-rc7 # perf test 1: vmlinux symtab matches kallsyms : Ok 2: Detect openat syscall event : Ok 3: Detect openat syscall event on all cpus : Ok 4: Read samples using the mmap interface : Ok 5: Test data source output : Ok 6: Parse event definition strings : Ok 7: Simple expression parser : Ok 8: PERF_RECORD_* events & perf_sample fields : Ok 9: Parse perf pmu format : Ok 10: DSO data read : Ok 11: DSO data cache : Ok 12: DSO data reopen : Ok 13: Roundtrip evsel->name : Ok 14: Parse sched tracepoints fields : Ok 15: syscalls:sys_enter_openat event fields : Ok 16: Setup struct perf_event_attr : Ok 17: Match and link multiple hists : Ok 18: 'import perf' in python : Ok 19: Breakpoint overflow signal handler : Ok 20: Breakpoint overflow sampling : Ok 21: Breakpoint accounting : Skip 22: Number of exit events of a simple workload : Ok 23: Software clock events period values : Ok 24: Object code reading : Ok 25: Sample parsing : Ok 26: Use a dummy software event to keep tracking : Ok 27: Parse with no sample_id_all bit set : Ok 28: Filter hist entries : Ok 29: Lookup mmap thread : Ok 30: Share thread mg : Ok 31: Sort output of hist entries : Ok 32: Cumulate child hist entries : Ok 33: Track with sched_switch : Ok 34: Filter fds with revents mask in a fdarray : Ok 35: Add fd to a fdarray, making it autogrow : Ok 36: kmod_path__parse : Ok 37: Thread map : Ok 38: LLVM search and compile : 38.1: Basic BPF llvm compile : Ok 38.2: kbuild searching : Ok 38.3: Compile source for BPF prologue generation : Ok 38.4: Compile source for BPF relocation : Ok 39: Session topology : Ok 40: BPF filter : 40.1: Basic BPF filtering : Ok 40.2: BPF pinning : Ok 40.3: BPF prologue generation : Ok 40.4: BPF relocation checker : Ok 41: Synthesize thread map : Ok 42: Remove thread map : Ok 43: Synthesize cpu map : Ok 44: Synthesize stat config : Ok 45: Synthesize stat : Ok 46: Synthesize stat round : Ok 47: Synthesize attr update : Ok 48: Event times : Ok 49: Read backward ring buffer : Ok 50: Print cpu map : Ok 51: Probe SDT events : Ok 52: is_printable_array : Ok 53: Print bitmap : Ok 54: perf hooks : Ok 55: builtin clang support : Skip (not compiled in) 56: unit_number__scnprintf : Ok 57: mem2node : Ok 58: x86 rdpmc : Ok 59: Convert perf time to TSC : Ok 60: DWARF unwind : Ok 61: x86 instruction decoder - new instructions : Ok 62: Use vfs_getname probe to get syscall args filenames : Ok 63: probe libc's inet_pton & backtrace it with ping : Ok 64: Check open filename arg using perf trace + vfs_getname: Ok 65: probe libc's inet_pton & backtrace it with ping : Ok 66: Add vfs_getname probe to get syscall args filenames : Ok #
$ make -C tools/perf build-test
make: Entering directory '/home/acme/git/perf/tools/perf'
- tarpkg: ./tests/perf-targz-src-pkg .
make_no_ui_O: make NO_NEWT=1 NO_SLANG=1 NO_GTK2=1
make_no_libperl_O: make NO_LIBPERL=1
make_no_libbionic_O: make NO_LIBBIONIC=1
make_install_prefix_O: make install prefix=/tmp/krava
make_perf_o_O: make perf.o
make_no_libpython_O: make NO_LIBPYTHON=1
make_tags_O: make tags
make_install_O: make install
make_doc_O: make doc
make_util_pmu_bison_o_O: make util/pmu-bison.o
make_no_libelf_O: make NO_LIBELF=1
make_install_bin_O: make install-bin
make_no_backtrace_O: make NO_BACKTRACE=1
make_no_gtk2_O: make NO_GTK2=1
make_no_slang_O: make NO_SLANG=1
make_no_libdw_dwarf_unwind_O: make NO_LIBDW_DWARF_UNWIND=1
make_with_babeltrace_O: make LIBBABELTRACE=1
make_help_O: make help
make_no_demangle_O: make NO_DEMANGLE=1
make_no_libbpf_O: make NO_LIBBPF=1
make_minimal_O: make NO_LIBPERL=1 NO_LIBPYTHON=1 NO_NEWT=1 NO_GTK2=1 NO_DEMANGLE=1 NO_LIBELF=1 NO_LIBUNWIND=1 NO_BACKTRACE=1 NO_LIBNUMA=1 NO_LIBAUDIT=1 NO_LIBBIONIC=1 NO_LIBDW_DWARF_UNWIND=1 NO_AUXTRACE=1 NO_LIBBPF=1 NO_LIBCRYPTO=1 NO_SDT=1 NO_JVMTI=1
make_clean_all_O: make clean all
make_no_newt_O: make NO_NEWT=1
make_no_libaudit_O: make NO_LIBAUDIT=1
make_no_libunwind_O: make NO_LIBUNWIND=1
make_no_auxtrace_O: make NO_AUXTRACE=1
make_debug_O: make DEBUG=1
make_pure_O: make
make_no_libnuma_O: make NO_LIBNUMA=1
make_no_scripts_O: make NO_LIBPYTHON=1 NO_LIBPERL=1
make_static_O: make LDFLAGS=-static
make_with_clangllvm_O: make LIBCLANGLLVM=1
make_install_prefix_slash_O: make install prefix=/tmp/krava/
make_util_map_o_O: make util/map.o
OK
make: Leaving directory '/home/acme/git/perf/tools/perf'
$ Arnaldo Carvalho de Melo
maintainerPATCH 1/8 perf build: Fix check-headers.sh opts assignment
From: Jiri Olsa <[email protected]>
Currently the "opts" variable is not zero-ed and we keep on adding to it, ending up with:
$ check-headers.sh 2>&1 + opts=' "-B"' + opts=' "-B" "-B"' + opts=' "-B" "-B" "-B"' + opts=' "-B" "-B" "-B" "-B"' + opts=' "-B" "-B" "-B" "-B" "-B"' + opts=' "-B" "-B" "-B" "-B" "-B" "-B"'
Fix this by initializing it in the check() function, right before starting the loop.
--- tools/perf/check-headers.sh | 1 + 1 file changed, 1 insertion(+)
tools/perf/check-headers.sh +1 -0
@@ -59,6 +59,7 @@ check () { file=$1 shift + opts= while [ -n "$*" ]; do opts="$opts \"$1\"" shift
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 2/8 perf mmap: Fix accessing unmapped mmap in perf_mmap__read_done()
In reply to Arnaldo Carvalho de MeloFrom: Kan Liang <[email protected]>
There is a segmentation fault when running 'perf trace'. For example:
[root@jouet e]# perf trace -e *chdir -o /tmp/bla perf report --ignore-vmlinux -i ../perf.data
The perf_mmap__consume() could unmap the mmap. It needs to check the refcnt in perf_mmap__read_done().
--- tools/perf/util/mmap.c | 6 ++++++ 1 file changed, 6 insertions(+)
tools/perf/util/mmap.c +6 -0
@@ -317,5 +317,11 @@ int perf_mmap__push(struct perf_mmap *md, void *to,*/ void perf_mmap__read_done (struct perf_mmap *map) { +/* +* Check if event was unmapped due to a POLLHUP/POLLERR. +*/ +if (!refcount_read (&map->refcnt)) +return ; + map->prev =perf_mmap__read_head (map); }
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 3/8 perf mmap: Be consistent when checking for an unmaped ring buffer
In reply to Arnaldo Carvalho de MeloFrom: Arnaldo Carvalho de Melo <[email protected]>
The previous patch is insufficient to cure the reported 'perf trace' segfault, as it only cures the perf_mmap__read_done() case, moving the segfault to perf_mmap__read_init() functio, fix it by doing the same refcount check.
--- tools/perf/util/mmap.c | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-)
tools/perf/util/mmap.c +12 -1
@@ -234,7 +234,7 @@ static int overwrite_rb_find_range(void *buf, int mask, u64 *start, u64 *end)/* * Report the start and end of the available data in ringbuffer */ -int perf_mmap__read_init (struct perf_mmap *md) +static int __perf_mmap__read_init (struct perf_mmap *md) {u64 head =perf_mmap__read_head (md);u64 old = md->prev;
@@ -268,6 +268,17 @@ int perf_mmap__read_init(struct perf_mmap *md)return 0 ; } +int perf_mmap__read_init (struct perf_mmap *map) +{ +/* +* Check if event was unmapped due to a POLLHUP/POLLERR. +*/ +if (!refcount_read (&map->refcnt)) +return -ENOENT ; + +return __perf_mmap__read_init (map); +} +int perf_mmap__push (struct perf_mmap *md,void *to,int push (void *to,void *buf,size_t size)) {
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 4/8 perf vendor events s390: Add JSON files for IBM z10EC z10BC
In reply to Arnaldo Carvalho de MeloFrom: Thomas Richter <[email protected]>
Add CPU measurement counter facility event description files (JSON files) for IBM z10EC and z10BC.
--- tools/perf/pmu-events/arch/s390/cf_z10/basic.json | 74 ++++++++++++++ tools/perf/pmu-events/arch/s390/cf_z10/crypto.json | 98 ++++++++++++++++++ .../perf/pmu-events/arch/s390/cf_z10/extended.json | 110 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 2 + 4 files changed, 284 insertions(+) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/mapfile.csv
tools/perf/pmu-events/arch/s390/cf_z10/basic.json new file +74 -0
@@ -0,0 +1,74 @@ +[ + { + "EventCode": "0", + "EventName": "CPU_CYCLES", + "BriefDescription": "CPU Cycles", + "PublicDescription": "Cycle Count" + }, + { + "EventCode": "1", + "EventName": "INSTRUCTIONS", + "BriefDescription": "Instructions", + "PublicDescription": "Instruction Count" + }, + { + "EventCode": "2", + "EventName": "L1I_DIR_WRITES", + "BriefDescription": "L1I Directory Writes", + "PublicDescription": "Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "3", + "EventName": "L1I_PENALTY_CYCLES", + "BriefDescription": "L1I Penalty Cycles", + "PublicDescription": "Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "4", + "EventName": "L1D_DIR_WRITES", + "BriefDescription": "L1D Directory Writes", + "PublicDescription": "Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "5", + "EventName": "L1D_PENALTY_CYCLES", + "BriefDescription": "L1D Penalty Cycles", + "PublicDescription": "Level-1 D-Cache Penalty Cycle Count" + }, + { + "EventCode": "32", + "EventName": "PROBLEM_STATE_CPU_CYCLES", + "BriefDescription": "Problem-State CPU Cycles", + "PublicDescription": "Problem-State Cycle Count" + }, + { + "EventCode": "33", + "EventName": "PROBLEM_STATE_INSTRUCTIONS", + "BriefDescription": "Problem-State Instructions", + "PublicDescription": "Problem-State Instruction Count" + }, + { + "EventCode": "34", + "EventName": "PROBLEM_STATE_L1I_DIR_WRITES", + "BriefDescription": "Problem-State L1I Directory Writes", + "PublicDescription": "Problem-State Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "35", + "EventName": "PROBLEM_STATE_L1I_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1I Penalty Cycles", + "PublicDescription": "Problem-State Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "36", + "EventName": "PROBLEM_STATE_L1D_DIR_WRITES", + "BriefDescription": "Problem-State L1D Directory Writes", + "PublicDescription": "Problem-State Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "37", + "EventName": "PROBLEM_STATE_L1D_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1D Penalty Cycles", + "PublicDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count" + }, +]
tools/perf/pmu-events/arch/s390/cf_z10/crypto.json new file +98 -0
98 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/cf_z10/extended.json new file +110 -0
110 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/mapfile.csv new file +2 -0
@@ -0,0 +1,2 @@ +Family-model,Version,Filename,EventType +209[78],1,cf_z10,core
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 5/8 perf vendor events s390: Add JSON files for IBM z196
In reply to Arnaldo Carvalho de MeloFrom: Thomas Richter <[email protected]>
Add CPU measurement counter facility event description files (json files) for IBM z196.
--- tools/perf/pmu-events/arch/s390/cf_z196/basic.json | 74 +++++++++++ .../perf/pmu-events/arch/s390/cf_z196/crypto.json | 98 ++++++++++++++ .../pmu-events/arch/s390/cf_z196/extended.json | 146 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 1 + 4 files changed, 319 insertions(+) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/extended.json
tools/perf/pmu-events/arch/s390/cf_z196/basic.json new file +74 -0
@@ -0,0 +1,74 @@ +[ + { + "EventCode": "0", + "EventName": "CPU_CYCLES", + "BriefDescription": "CPU Cycles", + "PublicDescription": "Cycle Count" + }, + { + "EventCode": "1", + "EventName": "INSTRUCTIONS", + "BriefDescription": "Instructions", + "PublicDescription": "Instruction Count" + }, + { + "EventCode": "2", + "EventName": "L1I_DIR_WRITES", + "BriefDescription": "L1I Directory Writes", + "PublicDescription": "Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "3", + "EventName": "L1I_PENALTY_CYCLES", + "BriefDescription": "L1I Penalty Cycles", + "PublicDescription": "Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "4", + "EventName": "L1D_DIR_WRITES", + "BriefDescription": "L1D Directory Writes", + "PublicDescription": "Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "5", + "EventName": "L1D_PENALTY_CYCLES", + "BriefDescription": "L1D Penalty Cycles", + "PublicDescription": "Level-1 D-Cache Penalty Cycle Count" + }, + { + "EventCode": "32", + "EventName": "PROBLEM_STATE_CPU_CYCLES", + "BriefDescription": "Problem-State CPU Cycles", + "PublicDescription": "Problem-State Cycle Count" + }, + { + "EventCode": "33", + "EventName": "PROBLEM_STATE_INSTRUCTIONS", + "BriefDescription": "Problem-State Instructions", + "PublicDescription": "Problem-State Instruction Count" + }, + { + "EventCode": "34", + "EventName": "PROBLEM_STATE_L1I_DIR_WRITES", + "BriefDescription": "Problem-State L1I Directory Writes", + "PublicDescription": "Problem-State Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "35", + "EventName": "PROBLEM_STATE_L1I_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1I Penalty Cycles", + "PublicDescription": "Problem-State Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "36", + "EventName": "PROBLEM_STATE_L1D_DIR_WRITES", + "BriefDescription": "Problem-State L1D Directory Writes", + "PublicDescription": "Problem-State Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "37", + "EventName": "PROBLEM_STATE_L1D_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1D Penalty Cycles", + "PublicDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count" + }, +]
tools/perf/pmu-events/arch/s390/cf_z196/crypto.json new file +98 -0
98 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/cf_z196/extended.json new file +146 -0
146 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/mapfile.csv +1 -0
@@ -1,2 +1,3 @@ Family-model,Version,Filename,EventType 209[78],1,cf_z10,core +281[78],1,cf_z196,core
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 6/8 perf vendor events s390: Add JSON files for IBM zEC12 zBC12
In reply to Arnaldo Carvalho de MeloFrom: Thomas Richter <[email protected]>
Add CPU measurement counter facility event description files (json files) for IBM zEC12 and zBC12.
--- .../perf/pmu-events/arch/s390/cf_zec12/basic.json | 74 +++++++ .../perf/pmu-events/arch/s390/cf_zec12/crypto.json | 98 ++++++++++ .../pmu-events/arch/s390/cf_zec12/extended.json | 212 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 1 + 4 files changed, 385 insertions(+) create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/extended.json
tools/perf/pmu-events/arch/s390/cf_zec12/basic.json new file +74 -0
@@ -0,0 +1,74 @@ +[ + { + "EventCode": "0", + "EventName": "CPU_CYCLES", + "BriefDescription": "CPU Cycles", + "PublicDescription": "Cycle Count" + }, + { + "EventCode": "1", + "EventName": "INSTRUCTIONS", + "BriefDescription": "Instructions", + "PublicDescription": "Instruction Count" + }, + { + "EventCode": "2", + "EventName": "L1I_DIR_WRITES", + "BriefDescription": "L1I Directory Writes", + "PublicDescription": "Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "3", + "EventName": "L1I_PENALTY_CYCLES", + "BriefDescription": "L1I Penalty Cycles", + "PublicDescription": "Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "4", + "EventName": "L1D_DIR_WRITES", + "BriefDescription": "L1D Directory Writes", + "PublicDescription": "Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "5", + "EventName": "L1D_PENALTY_CYCLES", + "BriefDescription": "L1D Penalty Cycles", + "PublicDescription": "Level-1 D-Cache Penalty Cycle Count" + }, + { + "EventCode": "32", + "EventName": "PROBLEM_STATE_CPU_CYCLES", + "BriefDescription": "Problem-State CPU Cycles", + "PublicDescription": "Problem-State Cycle Count" + }, + { + "EventCode": "33", + "EventName": "PROBLEM_STATE_INSTRUCTIONS", + "BriefDescription": "Problem-State Instructions", + "PublicDescription": "Problem-State Instruction Count" + }, + { + "EventCode": "34", + "EventName": "PROBLEM_STATE_L1I_DIR_WRITES", + "BriefDescription": "Problem-State L1I Directory Writes", + "PublicDescription": "Problem-State Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "35", + "EventName": "PROBLEM_STATE_L1I_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1I Penalty Cycles", + "PublicDescription": "Problem-State Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "36", + "EventName": "PROBLEM_STATE_L1D_DIR_WRITES", + "BriefDescription": "Problem-State L1D Directory Writes", + "PublicDescription": "Problem-State Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "37", + "EventName": "PROBLEM_STATE_L1D_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1D Penalty Cycles", + "PublicDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count" + }, +]
tools/perf/pmu-events/arch/s390/cf_zec12/crypto.json new file +98 -0
98 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/cf_zec12/extended.json new file +212 -0
212 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/mapfile.csv +1 -0
@@ -1,3 +1,4 @@ Family-model,Version,Filename,EventType 209[78],1,cf_z10,core 281[78],1,cf_z196,core +282[78],1,cf_zec12,core
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 7/8 perf vendor events s390: Add JSON files for IBM z13
In reply to Arnaldo Carvalho de MeloFrom: Thomas Richter <[email protected]>
Add CPU measurement counter facility event description files (json files) for IBM z13.
--- tools/perf/pmu-events/arch/s390/cf_z13/basic.json | 74 +++++ tools/perf/pmu-events/arch/s390/cf_z13/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z13/extended.json | 338 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 1 + 4 files changed, 511 insertions(+) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/extended.json
tools/perf/pmu-events/arch/s390/cf_z13/basic.json new file +74 -0
@@ -0,0 +1,74 @@ +[ + { + "EventCode": "0", + "EventName": "CPU_CYCLES", + "BriefDescription": "CPU Cycles", + "PublicDescription": "Cycle Count" + }, + { + "EventCode": "1", + "EventName": "INSTRUCTIONS", + "BriefDescription": "Instructions", + "PublicDescription": "Instruction Count" + }, + { + "EventCode": "2", + "EventName": "L1I_DIR_WRITES", + "BriefDescription": "L1I Directory Writes", + "PublicDescription": "Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "3", + "EventName": "L1I_PENALTY_CYCLES", + "BriefDescription": "L1I Penalty Cycles", + "PublicDescription": "Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "4", + "EventName": "L1D_DIR_WRITES", + "BriefDescription": "L1D Directory Writes", + "PublicDescription": "Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "5", + "EventName": "L1D_PENALTY_CYCLES", + "BriefDescription": "L1D Penalty Cycles", + "PublicDescription": "Level-1 D-Cache Penalty Cycle Count" + }, + { + "EventCode": "32", + "EventName": "PROBLEM_STATE_CPU_CYCLES", + "BriefDescription": "Problem-State CPU Cycles", + "PublicDescription": "Problem-State Cycle Count" + }, + { + "EventCode": "33", + "EventName": "PROBLEM_STATE_INSTRUCTIONS", + "BriefDescription": "Problem-State Instructions", + "PublicDescription": "Problem-State Instruction Count" + }, + { + "EventCode": "34", + "EventName": "PROBLEM_STATE_L1I_DIR_WRITES", + "BriefDescription": "Problem-State L1I Directory Writes", + "PublicDescription": "Problem-State Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "35", + "EventName": "PROBLEM_STATE_L1I_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1I Penalty Cycles", + "PublicDescription": "Problem-State Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "36", + "EventName": "PROBLEM_STATE_L1D_DIR_WRITES", + "BriefDescription": "Problem-State L1D Directory Writes", + "PublicDescription": "Problem-State Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "37", + "EventName": "PROBLEM_STATE_L1D_PENALTY_CYCLES", + "BriefDescription": "Problem-State L1D Penalty Cycles", + "PublicDescription": "Problem-State Level-1 D-Cache Penalty Cycle Count" + }, +]
tools/perf/pmu-events/arch/s390/cf_z13/crypto.json new file +98 -0
98 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/cf_z13/extended.json new file +338 -0
338 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/mapfile.csv +1 -0
@@ -2,3 +2,4 @@ Family-model,Version,Filename,EventType 209[78],1,cf_z10,core 281[78],1,cf_z196,core 282[78],1,cf_zec12,core +296[45],1,cf_z13,core
Signature · 1 line
2.14.3
Arnaldo Carvalho de Melo
maintainerPATCH 8/8 perf vendor events s390: Add JSON files for IBM z14
In reply to Arnaldo Carvalho de MeloFrom: Thomas Richter <[email protected]>
Add CPU measurement counter facility event description files (json files) for IBM z14.
--- tools/perf/pmu-events/arch/s390/cf_z14/basic.json | 50 ++++ tools/perf/pmu-events/arch/s390/cf_z14/crypto.json | 98 +++++++ .../perf/pmu-events/arch/s390/cf_z14/extended.json | 320 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 1 + 4 files changed, 469 insertions(+) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/extended.json
tools/perf/pmu-events/arch/s390/cf_z14/basic.json new file +50 -0
@@ -0,0 +1,50 @@ +[ + { + "EventCode": "0", + "EventName": "CPU_CYCLES", + "BriefDescription": "CPU Cycles", + "PublicDescription": "Cycle Count" + }, + { + "EventCode": "1", + "EventName": "INSTRUCTIONS", + "BriefDescription": "Instructions", + "PublicDescription": "Instruction Count" + }, + { + "EventCode": "2", + "EventName": "L1I_DIR_WRITES", + "BriefDescription": "L1I Directory Writes", + "PublicDescription": "Level-1 I-Cache Directory Write Count" + }, + { + "EventCode": "3", + "EventName": "L1I_PENALTY_CYCLES", + "BriefDescription": "L1I Penalty Cycles", + "PublicDescription": "Level-1 I-Cache Penalty Cycle Count" + }, + { + "EventCode": "4", + "EventName": "L1D_DIR_WRITES", + "BriefDescription": "L1D Directory Writes", + "PublicDescription": "Level-1 D-Cache Directory Write Count" + }, + { + "EventCode": "5", + "EventName": "L1D_PENALTY_CYCLES", + "BriefDescription": "L1D Penalty Cycles", + "PublicDescription": "Level-1 D-Cache Penalty Cycle Count" + }, + { + "EventCode": "32", + "EventName": "PROBLEM_STATE_CPU_CYCLES", + "BriefDescription": "Problem-State CPU Cycles", + "PublicDescription": "Problem-State Cycle Count" + }, + { + "EventCode": "33", + "EventName": "PROBLEM_STATE_INSTRUCTIONS", + "BriefDescription": "Problem-State Instructions", + "PublicDescription": "Problem-State Instruction Count" + }, +]
tools/perf/pmu-events/arch/s390/cf_z14/crypto.json new file +98 -0
98 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/cf_z14/extended.json new file +320 -0
320 lines not on this page · raw message
tools/perf/pmu-events/arch/s390/mapfile.csv +1 -0
@@ -3,3 +3,4 @@ Family-model,Version,Filename,EventType 281[78],1,cf_z196,core 282[78],1,cf_zec12,core 296[45],1,cf_z13,core +3906,3,cf_z14,core
Signature · 1 line
2.14.3
Quoted 80 lines · Arnaldo Carvalho de Melo
Hi Ingo,
Please consider pulling,
- Arnaldo
Test results at the end of this message, as usual.
The following changes since commit
631fe154edb0a37308d0116a0f9b7bba9dca6218:perf/x86: Update
rdpmc_always_availablestatic key to the modern API (2018-03-27 07:53:00 +0200)are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.gittags/perf-core-for-mingo-4.17-20180328for you to fetch changes up to
109d59b900e78834c66657dd4748fcedb9a1fe8d:perf vendor events s390: Add JSON files for IBM z14 (2018-03-27 13:13:39 -0300)
----------------------------------------------------------------
perf/core improvements and fixes:- Be consistent when checking if a
perf_mmapinstance had its ring buffer unmmaped, fixing segfaults noticed in 'perf trace' (Kan Liang, Arnaldo Carvalho de Melo)- Avoid adding the same option multiple times to the 'diff' command in
check-headers.sh(Jiri Olsa)- Add vendor event files (JSON format) to various IBM s390 models (z10EC, z10BC, z196, zEC12, zBC12, z13 and z14) (Thomas Richter)
Signed-off-by Arnaldo Carvalho de Melo <[email protected]>----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
perf mmap: Be consistent when checking for an unmaped ring bufferJiri Olsa (1):
perf build: Fixcheck-headers.shopts assignmentKan Liang (1):
perf mmap: Fix accessing unmapped mmap inperf_mmap__read_done()Thomas Richter (5):
perf vendor events s390: Add JSON files for IBM z10EC z10BC perf vendor events s390: Add JSON files for IBM z196 perf vendor events s390: Add JSON files for IBM zEC12 zBC12 perf vendor events s390: Add JSON files for IBM z13 perf vendor events s390: Add JSON files for IBM z14tools/perf/check-headers.sh | 1 + tools/perf/pmu-events/arch/s390/cf_z10/basic.json | 74 +++++ tools/perf/pmu-events/arch/s390/cf_z10/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z10/extended.json | 110 +++++++ tools/perf/pmu-events/arch/s390/cf_z13/basic.json | 74 +++++ tools/perf/pmu-events/arch/s390/cf_z13/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z13/extended.json | 338 +++++++++++++++++++++ tools/perf/pmu-events/arch/s390/cf_z14/basic.json | 50 +++ tools/perf/pmu-events/arch/s390/cf_z14/crypto.json | 98 ++++++ .../perf/pmu-events/arch/s390/cf_z14/extended.json | 320 +++++++++++++++++++ tools/perf/pmu-events/arch/s390/cf_z196/basic.json | 74 +++++ .../perf/pmu-events/arch/s390/cf_z196/crypto.json | 98 ++++++ .../pmu-events/arch/s390/cf_z196/extended.json | 146 +++++++++ .../perf/pmu-events/arch/s390/cf_zec12/basic.json | 74 +++++ .../perf/pmu-events/arch/s390/cf_zec12/crypto.json | 98 ++++++ .../pmu-events/arch/s390/cf_zec12/extended.json | 212 +++++++++++++ tools/perf/pmu-events/arch/s390/mapfile.csv | 6 + tools/perf/util/mmap.c | 19 +- 18 files changed, 1987 insertions(+), 1 deletion(-) create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z10/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z13/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/crypto.json
Quoted 8 lines
create mode 100644 tools/perf/pmu-events/arch/s390/cf_z14/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_z196/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/basic.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/crypto.json create mode 100644 tools/perf/pmu-events/arch/s390/cf_zec12/extended.json create mode 100644 tools/perf/pmu-events/arch/s390/mapfile.csv
Pulled, thanks a lot Arnaldo!
Ingo