mbox series

[v1,0/8] selftests: arm64: SVE ptrace test rework

Message ID 20210913125505.52619-1-broonie@kernel.org (mailing list archive)
Headers show
Series selftests: arm64: SVE ptrace test rework | expand

Message

Mark Brown Sept. 13, 2021, 12:54 p.m. UTC
This series overhauls the selftests we have for the SVE ptrace interface
to make them much more comprehensive than they are currently, making the
coverage of the data read and written more complete.  The new coverage
for setting data on all vector lengths showed the issue with using the
wrong buffer size with ptrace reported and fixed by:

  https://lore.kernel.org/linux-arm-kernel/20210909165356.10675-1-broonie@kernel.org/

(arm64/sve: Use correct size when reinitialising SVE state).

Mark Brown (8):
  selftests: arm64: Use a define for the number of SVE ptrace tests to
    be run
  selftests: arm64: Don't log child creation as a test in SVE ptrace
    test
  selftests: arm64: Remove extraneous register setting code
  selftests: arm64: Document what the SVE ptrace test is doing
  selftests: arm64: Clarify output when verifying SVE register set
  selftests: arm64: Verify interoperation of SVE and FPSIMD register
    sets
  selftests: arm64: More comprehensively test the SVE ptrace interface
  selftests: arm64: Move FPSIMD in SVE ptrace test into a function

 tools/testing/selftests/arm64/fp/Makefile     |   2 +-
 tools/testing/selftests/arm64/fp/TODO         |   9 +-
 .../selftests/arm64/fp/sve-ptrace-asm.S       |  33 --
 tools/testing/selftests/arm64/fp/sve-ptrace.c | 460 ++++++++++++------
 4 files changed, 321 insertions(+), 183 deletions(-)
 delete mode 100644 tools/testing/selftests/arm64/fp/sve-ptrace-asm.S


base-commit: 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f

Comments

Will Deacon Sept. 29, 2021, 5:48 p.m. UTC | #1
On Mon, 13 Sep 2021 13:54:57 +0100, Mark Brown wrote:
> This series overhauls the selftests we have for the SVE ptrace interface
> to make them much more comprehensive than they are currently, making the
> coverage of the data read and written more complete.  The new coverage
> for setting data on all vector lengths showed the issue with using the
> wrong buffer size with ptrace reported and fixed by:
> 
>   https://lore.kernel.org/linux-arm-kernel/20210909165356.10675-1-broonie@kernel.org/
> 
> [...]

Applied to arm64 (for-next/kselftest), thanks!

[1/8] selftests: arm64: Use a define for the number of SVE ptrace tests to be run
      https://git.kernel.org/arm64/c/78d2d816c45a
[2/8] selftests: arm64: Don't log child creation as a test in SVE ptrace test
      https://git.kernel.org/arm64/c/09121ad7186e
[3/8] selftests: arm64: Remove extraneous register setting code
      https://git.kernel.org/arm64/c/eab281e3afa6
[4/8] selftests: arm64: Document what the SVE ptrace test is doing
      https://git.kernel.org/arm64/c/736e6d5a5451
[5/8] selftests: arm64: Clarify output when verifying SVE register set
      https://git.kernel.org/arm64/c/8c9eece0bfbf
[6/8] selftests: arm64: Verify interoperation of SVE and FPSIMD register sets
      https://git.kernel.org/arm64/c/9f7d03a2c5a1
[7/8] selftests: arm64: More comprehensively test the SVE ptrace interface
      https://git.kernel.org/arm64/c/a1d7111257cd
[8/8] selftests: arm64: Move FPSIMD in SVE ptrace test into a function
      https://git.kernel.org/arm64/c/34785030dc06

Cheers,