diff options
| author | Veronika Molnarova <[email protected]> | 2023-12-01 20:46:17 +0100 |
|---|---|---|
| committer | Arnaldo Carvalho de Melo <[email protected]> | 2023-12-04 16:42:25 -0300 |
| commit | 28b01743ca752cea5ab182297d8b912b22f2a2d1 (patch) | |
| tree | 982d43338c6d7d091cf9fe9a1b804913fb769059 /tools/perf/scripts/python/bin/flamegraph-record | |
| parent | 4acef67646f35e14d202d5f534c0fd68d7691b22 (diff) | |
perf test record user-regs: Fix mask for vg register
The 'vg' register for arm64 shows up in --user_regs as available when
masking the variable AT_HWCAP with 1 << 22 returns '1' as done in
perf_regs.c.
However, in subtests for support of SVE, the check for the 'vg' register
is done by masking the variable AT_HWCAP with the value 0x200000 which
is equals to 1 << 21 instead of 1 << 22.
This results in inconsistencies on certain systems where the test
expects that the 'vg' register is not operational when it is, and
vice-versa.
During the testing on a machine that the test expected not to have the
'vg' register available, 'perf record' with the option --user-regs
showed records for the 'vg' register together with all of the others,
which means that the mask for the subtest of perf_event_attr is off by
one.
Change the value of the mask from 0x200000 to 0x400000 to correct it.
Fixes: 9440ebdc333dd12e ("perf test arm64: Add attr tests for new VG register")
Reviewed-by: Leo Yan <[email protected]>
Signed-off-by: Veronika Molnarova <[email protected]>
Cc: James Clark <[email protected]>
Cc: Michael Petlan <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/flamegraph-record')
0 files changed, 0 insertions, 0 deletions