linux.git/tools/testing/selftests/powerpc/benchmarks, branch v4.13

selftests/powerpc: context_switch use private futexes with threads

2017-06-05T06:55:01+00:00

This reduces overhead of mutex locking and increases context switch
rate significantly (which helps to measure and profile the context
switch path).

Signed-off-by: Nicholas Piggin 
Signed-off-by: Michael Ellerman

selftests/powerpc: Fix remaining fallout from recent changes

2017-02-14T15:02:27+00:00

In benchmarks we need to use $(TEST_GEN_PROGS) after we include lib.mk,
because lib.mk does the substitution to add $(OUTPUT).

In math the vmx and fpu names were typoed so they no longer matched
correctly, put back the 'v' and 'f'.

In tm we need to substitute $(OUTPUT) into SIGNAL_CONTEXT_CHK_TESTS so
that the rule matches.

In pmu there is an extraneous ':' on the end of $$BUILD_TARGET for the
clean and install rules, which breaks the logic in the child Makefiles.

Fixes: a8ba798bc8ec ("selftests: enable O and KBUILD_OUTPUT")
Signed-off-by: Michael Ellerman 
Signed-off-by: Shuah Khan

selftests: enable O and KBUILD_OUTPUT

2017-01-05T20:42:22+00:00

Enable O and KBUILD_OUTPUT for kselftest. User could compile kselftest
to another directory by passing O or KBUILD_OUTPUT. And O is high
priority than KBUILD_OUTPUT.

Signed-off-by: Bamvor Jian Zhang 
Signed-off-by: Shuah Khan

selftests: remove duplicated all and clean target

2017-01-05T20:41:35+00:00

Currently, kselftest use TEST_PROGS, TEST_PROGS_EXTENDED, TEST_FILES to
indicate the test program, extended test program and test files. It is
easy to understand the purpose of these files. But mix of compiled and
uncompiled files lead to duplicated "all" and "clean" targets.

In order to remove the duplicated targets, introduce TEST_GEN_PROGS,
TEST_GEN_PROGS_EXTENDED, TEST_GEN_FILES to indicate the compiled
objects.

Also, the later patch will make use of TEST_GEN_XXX to redirect these
files to output directory indicated by KBUILD_OUTPUT or O.

And add this changes to "Contributing new tests(details)" of
Documentation/kselftest.txt.

Signed-off-by: Bamvor Jian Zhang 
Signed-off-by: Shuah Khan

selftests/powerpc: Move shared headers into new include dir

2016-11-17T06:11:47+00:00

There are some functions, especially register related, which can
be shared across multiple selftests/powerpc test directories.

This patch creates a new include directory to store those shared
files, so that the file layout becomes more neat.

Signed-off-by: Simon Guo 
[mpe: Reworked to move the headers only]
Signed-off-by: Michael Ellerman

selftests/powerpc: Add Anton's null_syscall benchmark to the selftests

2016-11-14T00:11:51+00:00

Pull in a version of Anton's null_syscall benchmark:
  http://ozlabs.org/~anton/junkcode/null_syscall.c

Suggested-by: Michael Ellerman 
Signed-off-by: Anton Blanchard 
Signed-off-by: Rui Teng 
Signed-off-by: Michael Ellerman

selftests/powerpc: Import Anton's mmap & futex micro benchmarks

2016-07-05T13:49:50+00:00

These are useful little loops for smoke testing performance.

Signed-off-by: Anton Blanchard 
Signed-off-by: Michael Ellerman

selftests/powerpc: Fix generation of vector instructions/types in context_switch

2016-07-05T13:49:50+00:00

Currently it doesn't appear the resulting binary actually uses any
Altivec or VSX instructions the solution is to explicitly tell GCC to
use vector instructions and use vector types in the code.

Part of this this issue can be GCC version specific:

GCC 4.9.x is happy to use Altivec and VSX instructions if altivec.h is
includedi (and possibly if vector types are used), this also means that
4.9.x will use VSX instructions even if only -maltivec is passed. It is
also possible that Altivec instructions will be used even without
-maltivec or -mabi=altivec.

GCC 5.2.x complains about the lack of -maltivec parameter if altivec.h
is included and will not use VSX unless -mvsx is present on commandline.

GCC 5.3.0 has a regression that means __attribute__((__target__("no-vsx"))
fails to build. A fix is targeted for 5.4.

Furthermore LTO (Link Time Optimisation) doesn't play well with
__attribute__((__target__("no-vsx")), LTO can cause GCC to forget about
the attribute and compile with VSX instructions regardless. Be wary when
enabling -flfo for this test.

Signed-off-by: Cyril Bur 
Signed-off-by: Michael Ellerman

selftests/powerpc: Fix usage message in context_switch

2016-07-05T13:49:49+00:00

When we inverted the behaviour of the flags we forgot to update the
usage message.

Fixes: 51c21e72eb99 ("selftests/powerpc: Make context_switch touch FP/altivec/vector by default")
Signed-off-by: Cyril Bur 
Signed-off-by: Michael Ellerman

selftests/powerpc: Make context_switch touch FP/altivec/vector by default

2015-12-16T23:46:43+00:00

Simply because it touches more code paths that way, and therefore tests
more things.

Signed-off-by: Michael Ellerman 
Acked-by: Anton Blanchard