kselftest/arm64: Limit the maximum VL we try to set via ptrace
authorMark Brown <broonie@kernel.org>
Wed, 11 Jan 2023 15:02:41 +0000 (15:02 +0000)
committerCatalin Marinas <catalin.marinas@arm.com>
Tue, 31 Jan 2023 15:33:23 +0000 (15:33 +0000)
commit89ff30b9b72079a1c677500218bdc511eac246d4
treebdfb62d50f7eb4dcb55b44bccf63fc14dc8c87e7
parentdaac835347a52d9d141be281e4657cc08a360e97
kselftest/arm64: Limit the maximum VL we try to set via ptrace

When SVE was initially merged we chose to export the maximum VQ in the ABI
as being 512, rather more than the architecturally supported maximum of 16.
For the ptrace tests this results in us generating a lot of test cases and
hence log output which are redundant since a system couldn't possibly
support them. Instead only check values up to the current architectural
limit, plus one more so that we're covering the constraining of higher
vector lengths.

This makes no practical difference to our test coverage, speeds things up
on slower consoles and makes the output much more managable.

Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20230111-arm64-kselftest-ptrace-max-vl-v1-1-8167f41d1ad8@kernel.org
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
tools/testing/selftests/arm64/fp/sve-ptrace.c
tools/testing/selftests/arm64/fp/za-ptrace.c