linux

iv/linux

History

Mark Brown 48f7ab21f7 kselftest/arm64: Log SVCR when the SME tests barf

On failure we log the actual and expected value of the register we detect
a mismatch in. For SME one obvious potential source of corruption would be
if we had corrupted SVCR since changes in streaming mode will reset the
register values, log the value to aid in understanding issues.

Signed-off-by: Mark Brown <broonie@kernel.org>
Link: https://lore.kernel.org/r/20231205-arm64-kselftest-log-svcr-v1-1-b77abd9ee7f3@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>

2023-12-11 12:02:00 +00:00

abi

kselftest/arm64: Improve output for skipped TPIDR2 ABI test

2023-12-11 12:00:43 +00:00

bti

kselftest/arm64: build BTI tests in output directory

2023-08-16 14:43:47 +01:00

kselftest/arm64: Log SVCR when the SME tests barf

2023-12-11 12:02:00 +00:00

mte

kselftest/arm64: Remove spurious comment from MTE test Makefile

2023-01-20 14:30:46 +00:00

pauth

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

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

signal

kselftest/arm64: fix a memleak in zt_regs_run()

2023-08-16 14:17:06 +01: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