linux-toradex.git/tools/testing/selftests/memory-hotplug, branch v4.14-rc3

selftests: fix memory-hotplug test

2017-06-30T16:06:23+00:00

In the memory offline test, the $ration was used with RANDOM as the
possibility to get it offlined, correct it to become the portion of
available removable memory blocks.

Also ask the tool to try to offline the next available memory block
if the attempt is unsuccessful. It will only fail if all removable
memory blocks are busy.

A nice example:
$ sudo ./test.sh
Test scope: 10% hotplug memory
	online all hot-pluggable memory in offline state:
		SKIPPED - no hot-pluggable memory in offline state
	offline 10% hot-pluggable memory in online state
	trying to offline 3 out of 28 memory block(s):
online->offline memory1
online->offline memory10
./test.sh: line 74: echo: write error: Resource temporarily unavailable
offline_memory_expect_success 10: unexpected fail
online->offline memory100
online->offline memory101
	online all hot-pluggable memory in offline state:
offline->online memory1
offline->online memory100
offline->online memory101
skip extra tests: debugfs is not mounted
$ echo $?
0

Signed-off-by: Po-Hsu Lin 
Signed-off-by: Shuah Khan

selftests: add missing test name in memory-hotplug test

2017-06-30T16:06:23+00:00

There is no prompt for testing memory notifier error injection,
added with the same echo format of other tests above.

Signed-off-by: Po-Hsu Lin 
Signed-off-by: Shuah Khan

selftests: check percentage range for memory-hotplug test

2017-06-30T16:06:22+00:00

Check the precentage range for -r flag in memory-hotplug test.

Signed-off-by: Po-Hsu Lin 
Signed-off-by: Shuah Khan

selftests: check hot-pluggagble memory for memory-hotplug test

2017-06-30T16:06:22+00:00

Check for hot-pluggable memory availability in prerequisite() of the
memory-hotplug test.

Signed-off-by: Po-Hsu Lin 
Signed-off-by: Shuah Khan

selftests: typo correction for memory-hotplug test

2017-06-30T16:06:21+00:00

Typo fixed for hotpluggable_offline_memory() in memory-hotplug test.

Signed-off-by: Po-Hsu Lin 
Signed-off-by: Shuah Khan

selftests: create test-specific kconfig fragments

2016-02-25T16:47:52+00:00

Create the config file in each directory of testcase which need
more kernel configuration than the default defconfig. User could
use these configs with merge_config.sh script:

Enable config for specific testcase:
(export ARCH=xxx #for cross compiling)
./scripts/kconfig/merge_config.sh .config \
		tools/testing/selftests/xxx/config

Enable configs for all testcases:
(export ARCH=xxx #for cross compiling)
./scripts/kconfig/merge_config.sh .config \
		tools/testing/selftests/*/config

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

selftests: Change memory on-off-test.sh name to be unique

2015-04-01T16:33:02+00:00

cpu and memory hotplug scripts use the same name. Change
memory on-off-test.sh to mem-on-off-test.sh.

Signed-off-by: Shuah Khan 
Acked-by: Greg Kroah-Hartman

selftests: Add install target

2015-03-13T21:21:56+00:00

This adds make install support to selftests. The basic usage is:

$ cd tools/testing/selftests
$ make install

That installs into tools/testing/selftests/install, which can then be
copied where ever necessary.

The install destination is also configurable using eg:

$ INSTALL_PATH=/mnt/selftests make install

The implementation uses two targets in the child makefiles. The first
"install" is expected to install all files into $(INSTALL_PATH).

The second, "emit_tests", is expected to emit the test instructions (ie.
bash script) on stdout. Separating this from install means the child
makefiles need no knowledge of the location of the test script.

Signed-off-by: Michael Ellerman 
Signed-off-by: Shuah Khan

selftests: Introduce minimal shared logic for running tests

2015-03-13T21:13:40+00:00

This adds a Make include file which most selftests can then include to
get the run_tests logic.

On its own this has the advantage of some reduction in repetition, and
also means the pass/fail message is defined in fewer places.

However the key advantage is it will allow us to implement install very
simply in a subsequent patch.

The default implementation just executes each program in $(TEST_PROGS).

We use a variable to hold the default implementation of $(RUN_TESTS)
because that gives us a clean way to override it if necessary, ie. using
override. The mount, memory-hotplug and mqueue tests use that to provide
a different implementation.

Tests are not run via /bin/bash, so if they are scripts they must be
executable, we add a+x to several.

Signed-off-by: Michael Ellerman 
Signed-off-by: Shuah Khan

tools: selftests - create a separate hotplug target for full range test

2014-07-12T01:13:06+00:00

On some systems, hot-plug tests could hang forever waiting for cpu and
memory to be ready to be offlined. A special hot-plug target is created
to run full range of hot-plug tests. In default mode, hot-plug tests run
in safe mode with a limited scope. In limited mode, cpu-hotplug test is
run on a single cpu as opposed to all hotplug capable cpus, and memory
hotplug test is run on 2% of hotplug capable memory instead of 10%. In
addition to the above change, cpu-hotplug is chnged to change processor
affinity to cpu 0 so it doesn't impact itself while the test runs.

Signed-off-by: Shuah Khan 
Cc: Kees Cook 
Cc: Michael Ellerman 
Cc: Benjamin Herrenschmidt 
Cc: Frederic Weisbecker 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman