Hi
On 13/08/2019 17:23, Dave Martin wrote:
^ Regarding the subject line, "boilerplate code" sounds a bit vague. Could we say something like "Add skeleton Makefile"?
Yes of course.
On Fri, Aug 02, 2019 at 06:02:50PM +0100, Cristian Marussi wrote:
Added a new arm64-specific empty subsystem amongst TARGETS of KSFT build framework; once populated with testcases, it will be possible to build and invoke the new KSFT TARGETS=arm64 related tests from the toplevel Makefile in the usual ways.
Signed-off-by: Cristian Marussi cristian.marussi@arm.com
Reviewed the build instructions reported in the README, to be more agnostic regarding user/device etc..
tools/testing/selftests/Makefile | 1 + tools/testing/selftests/arm64/Makefile | 51 ++++++++++++++++++++++++++ tools/testing/selftests/arm64/README | 43 ++++++++++++++++++++++ 3 files changed, 95 insertions(+) create mode 100644 tools/testing/selftests/arm64/Makefile create mode 100644 tools/testing/selftests/arm64/README
diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile index 25b43a8c2b15..1722dae9381a 100644 --- a/tools/testing/selftests/Makefile +++ b/tools/testing/selftests/Makefile @@ -1,5 +1,6 @@ # SPDX-License-Identifier: GPL-2.0 TARGETS = android +TARGETS += arm64 TARGETS += bpf TARGETS += breakpoints TARGETS += capabilities diff --git a/tools/testing/selftests/arm64/Makefile b/tools/testing/selftests/arm64/Makefile new file mode 100644 index 000000000000..03a0d4f71218 --- /dev/null +++ b/tools/testing/selftests/arm64/Makefile @@ -0,0 +1,51 @@ +# SPDX-License-Identifier: GPL-2.0 +# Copyright (C) 2019 ARM Limited
+# When ARCH not overridden for crosscompiling, lookup machine +ARCH ?= $(shell uname -m) +ARCH := $(shell echo $(ARCH) | sed -e s/aarch64/arm64/)
+ifeq ("x$(ARCH)", "xarm64") +SUBDIRS := +else +SUBDIRS := +endif
+CFLAGS := -Wall -O2 -g
+export CC +export CFLAGS
+all:
- @for DIR in $(SUBDIRS); do \
BUILD_TARGET=$(OUTPUT)/$$DIR; \mkdir -p $$BUILD_TARGET; \make OUTPUT=$$BUILD_TARGET -C $$DIR $@; \- done
+install: all
- @for DIR in $(SUBDIRS); do \
BUILD_TARGET=$(OUTPUT)/$$DIR; \make OUTPUT=$$BUILD_TARGET -C $$DIR $@; \- done
+run_tests: all
- @for DIR in $(SUBDIRS); do \
BUILD_TARGET=$(OUTPUT)/$$DIR; \make OUTPUT=$$BUILD_TARGET -C $$DIR $@; \- done
+# Avoid any output on non arm64 on emit_tests +emit_tests: all
- @for DIR in $(SUBDIRS); do \
BUILD_TARGET=$(OUTPUT)/$$DIR; \make OUTPUT=$$BUILD_TARGET -C $$DIR $@; \- done
+clean:
- @for DIR in $(SUBDIRS); do \
BUILD_TARGET=$(OUTPUT)/$$DIR; \make OUTPUT=$$BUILD_TARGET -C $$DIR $@; \- done
+.PHONY: all clean install run_tests emit_tests diff --git a/tools/testing/selftests/arm64/README b/tools/testing/selftests/arm64/README new file mode 100644 index 000000000000..dee3306071cc --- /dev/null +++ b/tools/testing/selftests/arm64/README @@ -0,0 +1,43 @@ +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:
- as standalone (example for signal tests)
$ make -C tools/testing/selftest/arm64/signal \INSTALL_PATH=<your-installation-path> installand then launching on the target device inside the installed path:$ <your-installed-path>/test_arm64_signals.sh [-k | -v]
- within the KSelfTest framework using standard Linux top-level-makefile
targets:$ make TARGETS=arm64 kselftest-clean$ make TARGETS=arm64 kselftest- Further details on building and running KFST can be found in:
Documentation/dev-tools/kselftest.rstThe next two paragraphs aren't relevant yet. Can we split them out of this patch and add them alongside the relevant code / Makefile changes?
Sure. I'm going to remove also standalone mode in V4 as elsewhere advised, so I'll drop part of this README too.
+- Tests can depend on some arch-specific definitions which can be found in a
- standard Kernel Headers installation in $(top_srcdir)/usr/include.
- Such Kernel Headers are automatically installed (via make headers_install)
- by KSFT framework itself in a dedicated directory when tests are launched
- via KSFT itself; when running standalone, instead, a Warning is issued
- if such headers cannot be found somewhere (we try to guess a few standard
- locations anyway)
+- Some of these tests may be related to possibly not implemented ARMv8
- features: depending on their implementation status on the effective HW
- we'll expect different results. The tests' harness will take care to check
- at run-time if the required features are supported and will act accordingly.
- Moreover, in order to avoid any kind of compile-time dependency on the
- toolchain (possibly due to the above mentioned not-implemented features),
- we make strictly use of direct 'S3_ sysreg' raw-encoding while checking for
- those features and/or lookin up sysregs.
This last paragraph is only relevant for people adding new tests. It probably makes sense to start "When adding new tests, try to avoid unnecessary toolchain dependencies where possible. [...]"
Cheers ---Dave
Cheers
Cristian