From: Leo Yan <leo.yan@linaro.org>
To: vmolnaro@redhat.com
Cc: linux-perf-users@vger.kernel.org, acme@kernel.org,
acme@redhat.com, mpetlan@redhat.com, james.clark@arm.com
Subject: Re: [PATCH] perf test record user-regs: Fix mask for vg register
Date: Sun, 3 Dec 2023 14:13:53 +0800 [thread overview]
Message-ID: <20231203061353.GA19079@leoy-huanghe> (raw)
In-Reply-To: <20231201194617.13012-1-vmolnaro@redhat.com>
On Fri, Dec 01, 2023 at 08:46:17PM +0100, vmolnaro@redhat.com wrote:
> From: Veronika Molnarova <vmolnaro@redhat.com>
>
> 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, the perf record with 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.
>
> Signed-off-by: Veronika Molnarova <vmolnaro@redhat.com>
LGTM, except I think it's good to add fix tag:
Fixes: 9440ebdc333d ("perf test arm64: Add attr tests for new VG register")
With above fix tag:
Reviewed-by: Leo Yan <leo.yan@linaro.org>
next prev parent reply other threads:[~2023-12-03 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 19:46 [PATCH] perf test record user-regs: Fix mask for vg register vmolnaro
2023-12-03 6:13 ` Leo Yan [this message]
2023-12-04 19:33 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231203061353.GA19079@leoy-huanghe \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=james.clark@arm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--cc=vmolnaro@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).