public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
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 6/6] kselftest/arm64: Test signal handler state modification in fp-stress
Date: Wed, 6 Nov 2024 11:33:03 +0000	[thread overview]
Message-ID: <ZytT7z1EN97RaKmo@J2N7QTR9R3> (raw)
In-Reply-To: <20241023-arm64-fp-stress-irritator-v1-6-a51af298d449@kernel.org>

On Wed, Oct 23, 2024 at 09:38:34PM +0100, Mark Brown wrote:
> Currently in fp-stress we test signal delivery to the test threads by
> sending SIGUSR2 which simply counts how many signals are delivered. The
> test programs now also all have a SIGUSR1 handler which for the threads
> doing userspace testing additionally modifies the floating point register
> state in the signal handler, verifying that when we return the saved
> register state is restored from the signal context as expected. Switch over
> to triggering that to validate that we are restoring as expected.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>

Acked-by: Mark Rutland <mark.rutland@arm.com>

Mark.

> ---
>  tools/testing/selftests/arm64/fp/fp-stress.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/arm64/fp/fp-stress.c b/tools/testing/selftests/arm64/fp/fp-stress.c
> index faac24bdefeb9436e2daf20b7250d0ae25ca23a7..3d477249dee0632b662b48582433d39323d18e18 100644
> --- a/tools/testing/selftests/arm64/fp/fp-stress.c
> +++ b/tools/testing/selftests/arm64/fp/fp-stress.c
> @@ -221,7 +221,7 @@ static void child_output(struct child_data *child, uint32_t events,
>  static void child_tickle(struct child_data *child)
>  {
>  	if (child->output_seen && !child->exited)
> -		kill(child->pid, SIGUSR2);
> +		kill(child->pid, SIGUSR1);
>  }
>  
>  static void child_stop(struct child_data *child)
> 
> -- 
> 2.39.2
> 


  reply	other threads:[~2024-11-06 12:07 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
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 [this message]
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=ZytT7z1EN97RaKmo@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