mirror-linux/tools/testing/selftests/arm64
tanze b225219a40 kselftest/arm64: Set default OUTPUT path when undefined
When running 'make' in tools/testing/selftests/arm64/ without explicitly
setting the OUTPUT variable, the build system will creates test
directories (e.g., /bti) in the root filesystem due to OUTPUT defaulting
to an empty string. This causes unintended pollution of the root directory.

This patch adds proper handling for the OUTPUT variable: Sets OUTPUT
to the current directory (.) if not specified

Signed-off-by: tanze <tanze@kylinos.cn>
Link: https://lore.kernel.org/r/20250515051839.3409658-1-tanze@kylinos.cn
Signed-off-by: Will Deacon <will@kernel.org>
2025-05-16 15:15:13 +01:00
..
abi kselftest/arm64: tpidr2: Adjust to new clone() behaviour 2025-05-08 15:45:24 +01:00
bti kselftest/arm64: build BTI tests in output directory 2023-08-16 14:43:47 +01:00
fp kselftest/arm64: fp-ptrace: Adjust to new inactive mode behaviour 2025-05-08 15:45:24 +01:00
gcs kselftest/arm64: Fix missing printf() argument in gcs/gcs-stress.c 2024-11-12 14:39:30 +00:00
mte kselftest/arm64: mte: Skip the hugetlb tests if MTE not supported on such mappings 2025-03-05 18:54:02 +00:00
pauth kselftest/arm64: Try harder to generate different keys during PAC tests 2024-11-12 15:05:44 +00:00
signal Merge branches 'for-next/gcs', 'for-next/probes', 'for-next/asm-offsets', 'for-next/tlb', 'for-next/misc', 'for-next/mte', 'for-next/sysreg', 'for-next/stacktrace', 'for-next/hwcap3', 'for-next/kselftest', 'for-next/crc32', 'for-next/guest-cca', 'for-next/haft' and 'for-next/scs', remote-tracking branch 'arm64/for-next/perf' into for-next/core 2024-11-14 12:07:16 +00:00
tags selftests: arm64: tags: remove the result script 2024-07-11 19:00:14 +01:00
Makefile kselftest/arm64: Set default OUTPUT path when undefined 2025-05-16 15:15:13 +01:00
README kselftest: arm64: extend toplevel skeleton Makefile 2019-11-08 11:10:30 +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