"perf all PMU test" picks the input events from "perf list --raw-dump pmu" list and runs "perf stat -e" for each of the event in the list. In case of powerpc, the PowerVM environment supports events from hv_24x7 and hv_gpci PMU which is of example format like below: - hv_24x7/CPM_ADJUNCT_INST,domain=?,core=?/ - hv_gpci/event,partition_id=?/ The value for "?" needs to be filled in depending on system and respective event. CPM_ADJUNCT_INST needs have core value and domain value. hv_gpci event needs partition_id. Similarly, there are other events for hv_24x7 and hv_gpci having "?" in event format. Hence skip these events on powerpc platform since values like partition_id, domain is specific to system and event.
Unified · Split
| @@ -5,6 +5,16 @@ · 4 unmodified lines | |||
| 5 | set -e | 5 | set -e |
| 6 | 6 | ||
| 7 | for p in $(perf list --raw-dump pmu); do | 7 | for p in $(perf list --raw-dump pmu); do |
| 8 | # In powerpc, skip the events for hv_24x7 and hv_gpci. | ||
| 9 | # These events needs input values to be filled in for | ||
| 10 | # core, chip, partition id based on system. | ||
| 11 | # Example: hv_24x7/CPM_ADJUNCT_INST,domain=?,core=?/ | ||
| 12 | # hv_gpci/event,partition_id=?/ | ||
| 13 | # Hence skip these events for ppc. | ||
| 14 | if echo "$p" |grep -Eq 'hv_24x7|hv_gpci' ; then | ||
| 15 | echo "Skipping: Event '$p' in powerpc" | ||
| 16 | continue | ||
| 17 | fi | ||
| 8 | echo "Testing $p" | 18 | echo "Testing $p" |
| 9 | result=$(perf stat -e "$p" true 2>&1) | 19 | result=$(perf stat -e "$p" true 2>&1) |
| 10 | if ! echo "$result" | grep -q "$p" && ! echo "$result" | grep -q "<not supported>" ; then | 20 | if ! echo "$result" | grep -q "$p" && ! echo "$result" | grep -q "<not supported>" ; then |