tools/perf/tests: Update event_groups test to use instructions as one of the sibling event for hw type
PATCH 1/1 tools/perf/tests: Update event_groups test to use instructions as one of the sibling event for hw type
In some of the powerpc platforms, event group testcase fails as below:
# perf test -v 'Event groups' 69: Event groups : --- start --- test child forked, pid 9765 Using CPUID 0x00820200 Using hv_24x7 for uncore pmu event 0x0 0x0, 0x0 0x0, 0x0 0x0: Fail 0x0 0x0, 0x0 0x0, 0x1 0x3: Pass
The testcase creates various combinations of hw, sw and uncore PMU events and verify group creation succeeds or fails as expected. This tests one of the limitation in perf where it doesn't allow creating a group of events from different hw PMUs.
The testcase starts a leader event and opens two sibling events. The combination the fails is three hardware events in a group. "0x0 0x0, 0x0 0x0, 0x0 0x0: Fail"
Type zero and config zero which translates to PERF_TYPE_HARDWARE and PERF_COUNT_HW_CPU_CYCLE. There is event constraint in powerpc that events using same counter cannot be programmed in a group. Here there is one alternative event for cycles, hence one leader and only one sibling event can go in as a group.
if all three events (leader and two sibling events), are hardware events, use instructions as one of the sibling event. Since PERF_COUNT_HW_INSTRUCTIONS is a generic hardware event and present in all architectures, use this as third event.
--- tools/perf/tests/event_groups.c | 31 ++++++++++++++++++++++++++----- 1 file changed, 26 insertions(+), 5 deletions(-)
tools/perf/tests/event_groups.c +26 -5
@@ -10,9 +10,10 @@#include "header.h" #include "../perf-sys.h" -/* hw: cycles, sw: context-switch, uncore: [arch dependent] */ +/* hw: cycles,instructions sw: context-switch, uncore: [arch dependent] */ static int types[] = {0 ,1 ,-1 };static unsigned long configs[] = {0 ,3 ,0 }; +static unsigned long configs_hw[] = {1 };#define NR_UNCORE_PMUS 5
@@ -93,7 +94,18 @@ static int run_test(int i, int j, int k)return erroneous ?0 :-1 ; } - sibling_fd2 =event_open (types[k], configs[k], group_fd); +/* +* if all three events (leader and two sibling events) +* are hardware events, use instructions as one of the +* sibling event. There is event constraint in powerpc that +* events using same counter cannot be programmed in a group. +* Since PERF_COUNT_HW_INSTRUCTIONS is a generic hardware +* event and present in all platforms, lets use that. +*/ +if (!i && !j && !k) + sibling_fd2 =event_open (types[k], configs_hw[k], group_fd); +else + sibling_fd2 =event_open (types[k], configs[k], group_fd);if (sibling_fd2 ==-1 ) {close (sibling_fd1);close (group_fd);
@@ -124,9 +136,18 @@ static int test__event_groups(struct test_suite *text __maybe_unused, int subtesif (r) ret =TEST_FAIL ; -pr_debug ("0x%x 0x%lx, 0x%x 0x%lx, 0x%x 0x%lx: %s\n" , - types[i], configs[i], types[j], configs[j], - types[k], configs[k], r ?"Fail" :"Pass" ); +/* +* For all three events as HW events, second sibling +* event is picked from configs_hw. So print accordingly +*/ +if (!i && !j && !k) +pr_debug ("0x%x 0x%lx, 0x%x 0x%lx, 0x%x 0x%lx: %s\n" , + types[i], configs[i], types[j], configs[j], + types[k], configs_hw[k], r ?"Fail" :"Pass" ); +else +pr_debug ("0x%x 0x%lx, 0x%x 0x%lx, 0x%x 0x%lx: %s\n" , + types[i], configs[i], types[j], configs[j], + types[k], configs[k], r ?"Fail" :"Pass" ); } } }
Signature · 1 line
2.43.5
Hi Athira,
Quoted 20 lines · Athira Rajeev
In some of the powerpc platforms, event group testcase fails as below:
# perf test -v 'Event groups' 69: Event groups : --- start --- test child forked, pid 9765 Using CPUID 0x00820200 Using hv_24x7 for uncore pmu event 0x0 0x0, 0x0 0x0, 0x0 0x0: Fail 0x0 0x0, 0x0 0x0, 0x1 0x3: PassThe testcase creates various combinations of hw, sw and uncore PMU events and verify group creation succeeds or fails as expected. This tests one of the limitation in perf where it doesn't allow creating a group of events from different hw PMUs.
The testcase starts a leader event and opens two sibling events. The combination the fails is three hardware events in a group. "
0x00x0,0x00x0,0x00x0: Fail"
Quoted 5 lines
Type zero and config zero which translates to
PERF_TYPE_HARDWAREandPERF_COUNT_HW_CPU_CYCLE. There is event constraint in powerpc that events using same counter cannot be programmed in a group. Here there is one alternative event for cycles, hence one leader and only one sibling event can go in as a group.
For power9, cycles seems to map to PM_CYC event:
GENERIC_EVENT_ATTR(cpu-cycles, PM_CYC);
However, I don't see PM_CYC in power9_event_alternatives[]. Is PM_RUN_CYC and PM_CYC are same?
Thanks,
Ravi
Quoted 33 lines · Ravi Bangoria
Hi Athira,
Quoted 20 lines · Athira Rajeev
In some of the powerpc platforms, event group testcase fails as below:
# perf test -v 'Event groups' 69: Event groups : --- start --- test child forked, pid 9765 Using CPUID 0x00820200 Using hv_24x7 for uncore pmu event 0x0 0x0, 0x0 0x0, 0x0 0x0: Fail 0x0 0x0, 0x0 0x0, 0x1 0x3: PassThe testcase creates various combinations of hw, sw and uncore PMU events and verify group creation succeeds or fails as expected. This tests one of the limitation in perf where it doesn't allow creating a group of events from different hw PMUs.
The testcase starts a leader event and opens two sibling events. The combination the fails is three hardware events in a group. "
0x00x0,0x00x0,0x00x0: Fail"Quoted 5 lines
Type zero and config zero which translates to
PERF_TYPE_HARDWAREandPERF_COUNT_HW_CPU_CYCLE. There is event constraint in powerpc that events using same counter cannot be programmed in a group. Here there is one alternative event for cycles, hence one leader and only one sibling event can go in as a group.
Quoted 6 lines
For power9, cycles seems to map to
PM_CYCevent:GENERIC_EVENT_ATTR(cpu-cycles, PM_CYC);However, I don't see
PM_CYCin power9_event_alternatives[]. IsPM_RUN_CYCandPM_CYCare same?
Hi Ravi
They are not the same. PM_CYC count irrespective of the run latch state (idle state) whereas PM_RUN_CYC doesn’t do that.
This test runs fine in power9. The event code for PM_CYC isEVENT(PM_CYC, 0x0001e)
Here it is not specifically meant to be run a particular counter and even if no alternative event is defined, it can pick available counters and go in as a group. But there are cases like other PMU (which is used in absence of platform specific PMU) , where alternative event is specified to run a particular counter.
Example: arch/powerpc/perf/generic-compat-pmu.c
EVENT(PM_CYC_ALT, 0x100f0) EVENT(PM_CYC, 0x600f4)
In this case, we can have only two cycles events to go in a group. So with our testcase events, one leader and only one sibling event can go in a group (checked other PMU’s to confirm two is possible). So added this fix to consider instructions as one of the sibling event.
Thanks
Athira
Quoted 3 lines
Thanks,
Ravi
Ravi Bangoria
Reviewed-byQuoted 35 lines
Quoted 26 lines
Quoted 20 lines
In some of the powerpc platforms, event group testcase fails as below:
# perf test -v 'Event groups' 69: Event groups : --- start --- test child forked, pid 9765 Using CPUID 0x00820200 Using hv_24x7 for uncore pmu event 0x0 0x0, 0x0 0x0, 0x0 0x0: Fail 0x0 0x0, 0x0 0x0, 0x1 0x3: PassThe testcase creates various combinations of hw, sw and uncore PMU events and verify group creation succeeds or fails as expected. This tests one of the limitation in perf where it doesn't allow creating a group of events from different hw PMUs.
The testcase starts a leader event and opens two sibling events. The combination the fails is three hardware events in a group. "
0x00x0,0x00x0,0x00x0: Fail"Quoted 5 lines
Type zero and config zero which translates to
PERF_TYPE_HARDWAREandPERF_COUNT_HW_CPU_CYCLE. There is event constraint in powerpc that events using same counter cannot be programmed in a group. Here there is one alternative event for cycles, hence one leader and only one sibling event can go in as a group.Quoted 6 lines
For power9, cycles seems to map to
PM_CYCevent:GENERIC_EVENT_ATTR(cpu-cycles, PM_CYC);However, I don't see
PM_CYCin power9_event_alternatives[]. IsPM_RUN_CYCandPM_CYCare same?Hi Ravi
Quoted 7 lines
They are not the same.
PM_CYCcount irrespective of the run latch state (idle state) whereasPM_RUN_CYCdoesn’t do that.This test runs fine in power9. The event code for
PM_CYCisEVENT(PM_CYC, 0x0001e)Here it is not specifically meant to be run a particular counter and even if no alternative event is defined, it can pick available counters and go in as a group.
Got it.
Quoted 8 lines
But there are cases like other PMU (which is used in absence of platform specific PMU) , where alternative event is specified to run a particular counter.
Example:arch/powerpc/perf/generic-compat-pmu.cEVENT(PM_CYC_ALT, 0x100f0) EVENT(PM_CYC, 0x600f4)In this case, we can have only two cycles events to go in a group. So with our testcase events, one leader and only one sibling event can go in a group (checked other PMU’s to confirm two is possible). So added this fix to consider instructions as one of the sibling event.
Thanks for the explanation.
Thanks,
Ravi
Quoted 11 lines · Athira Rajeev
In some of the powerpc platforms, event group testcase fails as below:
# perf test -v 'Event groups' 69: Event groups : --- start --- test child forked, pid 9765 Using CPUID 0x00820200 Using hv_24x7 for uncore pmu event 0x0 0x0, 0x0 0x0, 0x0 0x0: Fail 0x0 0x0, 0x0 0x0, 0x1 0x3: Pass
Quoted 1 line
[...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung