linux

iv/linux

History

Andre Przywara 5238c2cd5a kselftest/arm64: mte: Use cross-compiler if specified

At the moment we either need to provide CC explicitly, or use a native
machine to get the ARM64 MTE selftest compiled.

It seems useful to use the same (cross-)compiler as we use for the
kernel, so copy the recipe we use in the pauth selftest.

Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Mark Brown <broone@kernel.org>
Link: https://lore.kernel.org/r/20210319165334.29213-8-andre.przywara@arm.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>

2021-03-24 15:43:20 +00:00

kselftest: arm64: Fix exit code of sve-ptrace

2021-03-10 10:58:11 +00:00

mte

kselftest/arm64: mte: Use cross-compiler if specified

2021-03-24 15:43:20 +00:00

pauth

kselftests/arm64: add PAuth tests for single threaded consistency and differently initialized keys

2020-09-18 14:07:20 +01:00

signal

kselftest: arm64: Remove redundant clean target

2020-06-24 14:25:59 +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