[PATCH 0/7] Improvement kselftest support for arm and arm64

[Bamvor Jian Zhang]

This is my first attempt for improving the kselftest for arm/arm64
architecture. Eventually, we hope we could build(in an cross compile
environment) and run all the kselftest cases automatically(successful
of courses).

I realize that there are lots of improvement for kselftest after the
lastest pull request for kselftest. So, All my work is based on the
lastest linux-next tree ("30b42f4 Add linux-next specific files for
20150813").

In this series, I try to make all the testcases compiling and
installation successful.

Patch 1 rename jumplabel target to static_keys in the Makefile.

Patch 2 add CFLAGS_EXTRA to fix the cross comiling failure.

Patch 3 fix the running the installation issue for exec testcase.

Patch 4 check if there are files need to be installed. This is
useful when such testcase is not built for specific architecture.
E.g. x86 testcases for arm/arm64.

Patch 5, 6 and 7 check the architecture before build and install.

Bamvor Jian Zhang (7):
  selftests: rename jump label to static_keys
  selftests: add CFLAGS_EXTRA
  selftests: exec: fix for running and installing
  selftests: check before install
  selftests: disable seccomp for arm64
  selftests: only compile userfaultfd for x86 and powperpc
  selftests: breakpoints: fix installing error on the architecture
    except x86

 tools/testing/selftests/Makefile             |  3 +--
 tools/testing/selftests/breakpoints/Makefile | 16 +++-------------
 tools/testing/selftests/exec/Makefile        | 14 +++++++++++---
 tools/testing/selftests/lib.mk               | 15 ++++++++++-----
 tools/testing/selftests/seccomp/Makefile     |  6 ++++++
 tools/testing/selftests/vm/Makefile          | 12 ++++++++++++
 6 files changed, 43 insertions(+), 23 deletions(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/