linux

iv/linux

History

Mark Brown 9ae279ecab kselftest/arm64: Correct logging of FPSIMD register read via ptrace

There's a cut'n'paste error in the logging for our test for reading register
state back via ptrace, correctly say that we did a read instead of a write.

Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Link: https://lore.kernel.org/r/20220124175527.3260234-3-broonie@kernel.org
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

2022-01-28 11:30:51 +00:00

abi

kselftest/arm64: Add a test program to exercise the syscall ABI

2021-12-14 18:35:10 +00:00

bti

kselftest/arm64: Add missing stddef.h include to BTI tests

2021-05-10 10:19:01 +01:00

kselftest/arm64: Correct logging of FPSIMD register read via ptrace

2022-01-28 11:30:51 +00:00

mte

kselftest/arm64: mte: Fix misleading output when skipping tests

2021-08-20 11:11:05 +01:00

pauth

kselftest/arm64: pac: Fix skipping of tests on systems without PAC

2021-08-20 12:06:59 +01:00

signal

kselftest/arm64: Allow signal tests to trigger from a function

2021-12-14 18:35:10 +00:00

README

KSelfTest ARM64
===============

- These tests are arm64 specific and so not built or run but just skipped
  completely when env-variable ARCH is found to be different than 'arm64'
  and `uname -m` reports other than 'aarch64'.

- Holding true the above, ARM64 KSFT tests can be run within the KSelfTest
  framework using standard Linux top-level-makefile targets:

      $ make TARGETS=arm64 kselftest-clean
      $ make TARGETS=arm64 kselftest

      or

      $ make -C tools/testing/selftests TARGETS=arm64 \
		INSTALL_PATH=<your-installation-path> install

      or, alternatively, only specific arm64/ subtargets can be picked:

      $ make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS="tags signal" \
		INSTALL_PATH=<your-installation-path> install

   Further details on building and running KFST can be found in:
     Documentation/dev-tools/kselftest.rst