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>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] kselftest/arm64: Correct misleading comments on fp-stress irritators
Date: Wed, 6 Nov 2024 11:29:16 +0000 [thread overview]
Message-ID: <ZytTDJOfFaynG1rp@J2N7QTR9R3> (raw)
In-Reply-To: <20241023-arm64-fp-stress-irritator-v1-1-a51af298d449@kernel.org>
On Wed, Oct 23, 2024 at 09:38:29PM +0100, Mark Brown wrote:
> The comments in the handlers for the irritator signal in the test threads
> for fp-stress suggest that the irritator will corrupt the register state
> observed by the main thread but this is not the case, instead the FPSIMD
> and SVE irritators (which are the only ones that are implemented) modify
> the current register state which is expected to be overwritten on return
> from the handler by the saved register state. Update the comment to reflect
> what the handler is actually doing.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> tools/testing/selftests/arm64/fp/fpsimd-test.S | 3 +--
> tools/testing/selftests/arm64/fp/sve-test.S | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/arm64/fp/fpsimd-test.S b/tools/testing/selftests/arm64/fp/fpsimd-test.S
> index 8b960d01ed2e0ef516893b68794078ddf8c01e1f..bdfb7cf2e4ec175fda62c1c2f38c6ebb1a1c48bf 100644
> --- a/tools/testing/selftests/arm64/fp/fpsimd-test.S
> +++ b/tools/testing/selftests/arm64/fp/fpsimd-test.S
> @@ -134,8 +134,7 @@ function check_vreg
> b memcmp
> endfunction
>
> -// Any SVE register modified here can cause corruption in the main
> -// thread -- but *only* the registers modified here.
> +// Modify live register state, the signal return will undo our changes
> function irritator_handler
> // Increment the irritation signal count (x23):
> ldr x0, [x2, #ucontext_regs + 8 * 23]
> diff --git a/tools/testing/selftests/arm64/fp/sve-test.S b/tools/testing/selftests/arm64/fp/sve-test.S
> index fff60e2a25addfd4850ef71aa3cf6535ac880ffd..e3c0d585684df29723a49265f3df6d23817498c7 100644
> --- a/tools/testing/selftests/arm64/fp/sve-test.S
> +++ b/tools/testing/selftests/arm64/fp/sve-test.S
> @@ -291,8 +291,7 @@ function check_ffr
> #endif
> endfunction
>
> -// Any SVE register modified here can cause corruption in the main
> -// thread -- but *only* the registers modified here.
> +// Modify live register state, the signal return will undo our changes
> function irritator_handler
> // Increment the irritation signal count (x23):
> ldr x0, [x2, #ucontext_regs + 8 * 23]
>
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-11-06 12:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 20:38 [PATCH 0/6] kselftest/arm64: Test floating point signal context restore in fp-stress Mark Brown
2024-10-23 20:38 ` [PATCH 1/6] kselftest/arm64: Correct misleading comments on fp-stress irritators Mark Brown
2024-11-06 11:29 ` Mark Rutland [this message]
2024-10-23 20:38 ` [PATCH 2/6] kselftest/arm64: Remove unused ADRs from irritator handlers Mark Brown
2024-11-06 11:29 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 3/6] kselftest/arm64: Corrupt P15 in the irritator when testing SSVE Mark Brown
2024-11-06 11:27 ` Mark Rutland
2024-11-06 12:46 ` Mark Brown
2024-10-23 20:38 ` [PATCH 4/6] kselftest/arm64: Implement irritators for ZA and ZT Mark Brown
2024-11-06 11:31 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 5/6] kselftest/arm64: Provide a SIGUSR1 handler in the kernel mode FP stress test Mark Brown
2024-11-06 11:32 ` Mark Rutland
2024-10-23 20:38 ` [PATCH 6/6] kselftest/arm64: Test signal handler state modification in fp-stress Mark Brown
2024-11-06 11:33 ` Mark Rutland
2024-10-28 14:26 ` [PATCH 0/6] kselftest/arm64: Test floating point signal context restore " Mark Rutland
2024-10-28 15:38 ` Mark Brown
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=ZytTDJOfFaynG1rp@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=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