From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] kselftest/arm64: Specify SVE data when testing VL set in sve-ptrace
Date: Mon, 26 May 2025 11:57:38 +0100 [thread overview]
Message-ID: <aDRJIjTOAAe0U8or@J2N7QTR9R3> (raw)
In-Reply-To: <20250523-kselftest-arm64-ssve-fixups-v1-3-65069a263b21@kernel.org>
On Fri, May 23, 2025 at 04:27:14PM +0100, Mark Brown wrote:
> Since f916dd32a943 ("arm64/fpsimd: ptrace: Mandate SVE payload for
> streaming-mode state") we reject attempts to write to the streaming mode
> regset even if there is no register data supplied, causing the tests for
> setting vector lengths and setting SVE_VL_INHERIT in sve-ptrace to
> spuriously fail. Set the flag to avoid the issue, we still support not
> supplying register data.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> tools/testing/selftests/arm64/fp/sve-ptrace.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/arm64/fp/sve-ptrace.c b/tools/testing/selftests/arm64/fp/sve-ptrace.c
> index 7e259907805b..7f9b6a61d369 100644
> --- a/tools/testing/selftests/arm64/fp/sve-ptrace.c
> +++ b/tools/testing/selftests/arm64/fp/sve-ptrace.c
> @@ -170,7 +170,7 @@ static void ptrace_set_get_inherit(pid_t child, const struct vec_type *type)
> memset(&sve, 0, sizeof(sve));
> sve.size = sizeof(sve);
> sve.vl = sve_vl_from_vq(SVE_VQ_MIN);
> - sve.flags = SVE_PT_VL_INHERIT;
> + sve.flags = SVE_PT_VL_INHERIT | SVE_PT_REGS_SVE;
> ret = set_sve(child, type, &sve);
> if (ret != 0) {
> ksft_test_result_fail("Failed to set %s SVE_PT_VL_INHERIT\n",
> @@ -235,6 +235,7 @@ static void ptrace_set_get_vl(pid_t child, const struct vec_type *type,
> /* Set the VL by doing a set with no register payload */
> memset(&sve, 0, sizeof(sve));
> sve.size = sizeof(sve);
> + sve.flags = SVE_PT_REGS_SVE;
> sve.vl = vl;
> ret = set_sve(child, type, &sve);
> if (ret != 0) {
>
> --
> 2.39.5
>
next prev parent reply other threads:[~2025-05-26 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 15:27 [PATCH 0/3] kselftest/arm64: Update sve-ptrace for ABI changes Mark Brown
2025-05-23 15:27 ` [PATCH 1/3] kselftest/arm64: Fix check for setting new VLs in sve-ptrace Mark Brown
2025-05-26 10:30 ` Mark Rutland
2025-05-26 10:53 ` Dev Jain
2025-05-23 15:27 ` [PATCH 2/3] kselftest/arm64: Fix test for streaming FPSIMD write " Mark Brown
2025-05-26 10:44 ` Mark Rutland
2025-05-23 15:27 ` [PATCH 3/3] kselftest/arm64: Specify SVE data when testing VL set " Mark Brown
2025-05-26 10:57 ` Mark Rutland [this message]
2025-05-26 10:23 ` [PATCH 0/3] kselftest/arm64: Update sve-ptrace for ABI changes Mark Rutland
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=aDRJIjTOAAe0U8or@J2N7QTR9R3 \
--to=mark.rutland@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=will@kernel.org \
/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