Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Shuah Khan <shuah@kernel.org>, Dave Martin <Dave.Martin@arm.com>
Cc: linux-kselftest@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"skh >> Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 0/6] selftests: arm64: Add floating point selftests
Date: Mon, 31 Aug 2020 15:45:46 -0600	[thread overview]
Message-ID: <cd9979be-34a3-375d-0fa1-61937337ca14@linuxfoundation.org> (raw)
In-Reply-To: <20200819114837.51466-1-broonie@kernel.org>

On 8/19/20 5:48 AM, Mark Brown wrote:
> This series imports a series of tests for FPSIMD and SVE originally
> written by Dave Martin to the tree. Since these extensions have some
> overlap in terms of register usage and must sometimes be tested together
> they're dropped into a single directory. I've adapted some of the tests
> to run within the kselftest framework but there are also some stress
> tests here that are intended to be run as soak tests so aren't suitable
> for running by default and are mostly just integrated with the build
> system. There doesn't seem to be a more suitable home for those stress
> tests and they are very useful for work on these areas of the code so it
> seems useful to have them somewhere in tree.
> 
> v2: Rebased onto v5.9-rc1
> 
> Mark Brown (6):
>    selftests: arm64: Test case for enumeration of SVE vector lengths
>    selftests: arm64: Add test for the SVE ptrace interface
>    selftests: arm64: Add stress tests for FPSMID and SVE context
>      switching
>    selftests: arm64: Add utility to set SVE vector lengths
>    selftests: arm64: Add wrapper scripts for stress tests
>    selftests: arm64: Add build and documentation for FP tests
> 
>   tools/testing/selftests/arm64/Makefile        |   2 +-
>   tools/testing/selftests/arm64/fp/.gitignore   |   5 +
>   tools/testing/selftests/arm64/fp/Makefile     |  17 +
>   tools/testing/selftests/arm64/fp/README       | 100 +++
>   .../testing/selftests/arm64/fp/asm-offsets.h  |  11 +
>   tools/testing/selftests/arm64/fp/assembler.h  |  57 ++
>   .../testing/selftests/arm64/fp/fpsimd-stress  |  60 ++
>   .../testing/selftests/arm64/fp/fpsimd-test.S  | 482 +++++++++++++
>   .../selftests/arm64/fp/sve-probe-vls.c        |  58 ++
>   .../selftests/arm64/fp/sve-ptrace-asm.S       |  33 +
>   tools/testing/selftests/arm64/fp/sve-ptrace.c | 336 +++++++++
>   tools/testing/selftests/arm64/fp/sve-stress   |  59 ++
>   tools/testing/selftests/arm64/fp/sve-test.S   | 672 ++++++++++++++++++
>   tools/testing/selftests/arm64/fp/vlset.c      | 155 ++++
>   14 files changed, 2046 insertions(+), 1 deletion(-)
>   create mode 100644 tools/testing/selftests/arm64/fp/.gitignore
>   create mode 100644 tools/testing/selftests/arm64/fp/Makefile
>   create mode 100644 tools/testing/selftests/arm64/fp/README
>   create mode 100644 tools/testing/selftests/arm64/fp/asm-offsets.h
>   create mode 100644 tools/testing/selftests/arm64/fp/assembler.h
>   create mode 100755 tools/testing/selftests/arm64/fp/fpsimd-stress
>   create mode 100644 tools/testing/selftests/arm64/fp/fpsimd-test.S
>   create mode 100644 tools/testing/selftests/arm64/fp/sve-probe-vls.c
>   create mode 100644 tools/testing/selftests/arm64/fp/sve-ptrace-asm.S
>   create mode 100644 tools/testing/selftests/arm64/fp/sve-ptrace.c
>   create mode 100755 tools/testing/selftests/arm64/fp/sve-stress
>   create mode 100644 tools/testing/selftests/arm64/fp/sve-test.S
>   create mode 100644 tools/testing/selftests/arm64/fp/vlset.c
> 


Will,

Patches look good to me from selftests perspective. My acked by
for these patches to go through arm64.

Acked-by: Shuah Khan <skhan@linuxfoundation.org>

If you would like me to take these through kselftest tree, give
me your Acks. I can queue these up for 5.10-rc1

thanks,
-- Shuah

  parent reply	other threads:[~2020-08-31 21:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 11:48 [PATCH v2 0/6] selftests: arm64: Add floating point selftests Mark Brown
2020-08-19 11:48 ` [PATCH v2 1/6] selftests: arm64: Test case for enumeration of SVE vector lengths Mark Brown
2020-08-19 11:48 ` [PATCH v2 2/6] selftests: arm64: Add test for the SVE ptrace interface Mark Brown
2020-08-19 11:48 ` [PATCH v2 3/6] selftests: arm64: Add stress tests for FPSMID and SVE context switching Mark Brown
2020-08-19 11:48 ` [PATCH v2 4/6] selftests: arm64: Add utility to set SVE vector lengths Mark Brown
2020-08-19 11:48 ` [PATCH v2 5/6] selftests: arm64: Add wrapper scripts for stress tests Mark Brown
2020-08-19 11:48 ` [PATCH v2 6/6] selftests: arm64: Add build and documentation for FP tests Mark Brown
2020-09-01 15:38   ` Dave Martin
2020-09-01 15:47     ` Mark Brown
2020-09-01 16:06       ` Dave Martin
2020-08-31 21:45 ` Shuah Khan [this message]
2020-09-01 13:21   ` [PATCH v2 0/6] selftests: arm64: Add floating point selftests Will Deacon
2020-09-01 15:27     ` Dave Martin
2020-09-18 16:17 ` Will Deacon

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=cd9979be-34a3-375d-0fa1-61937337ca14@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=Dave.Martin@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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