linux

Files

Mark Brown e2dc49ef6c kselftest/arm64: Log the PIDs of the parent and child in sve-ptrace

If the test triggers a problem it may well result in a log message from
the kernel such as a WARN() or BUG(). If these include a PID it can help
with debugging to know if it was the parent or child process that triggered
the issue, since the test is just creating a new thread the process name
will be the same either way. Print the PIDs of the parent and child on
startup so users have this information to hand should it be needed.

Signed-off-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
Link: https://lore.kernel.org/r/20220303192817.2732509-1-broonie@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>

2022-03-07 21:46:57 +00:00

abi

kselftest/arm64: Remove local ARRAY_SIZE() definitions

2022-02-15 15:59:01 +00:00

bti

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

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

kselftest/arm64: Log the PIDs of the parent and child in sve-ptrace

2022-03-07 21:46:57 +00:00

mte

kselftest/arm64: mte: user_mem: test a wider range of values

2022-02-15 16:57:51 +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: signal: Allow tests to be incompatible with features

2022-02-25 14:38:29 +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