Lines Matching +full:custom +full:- +full:output +full:- +full:range +full:- +full:config
23 On some systems, hot-plug tests could hang forever waiting for cpu and
24 memory to be ready to be offlined. A special hot-plug target is created
25 to run the full range of hot-plug tests. In default mode, hot-plug tests run
26 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
40 $ make -C tools/testing/selftests
44 $ make -C tools/testing/selftests run_tests
52 Kselftest supports saving output files in a separate directory and then
53 running tests. To locate output files in a separate directory two syntaxes
58 To build, save output files in a separate directory with O= ::
62 To build, save output files in a separate directory with KBUILD_OUTPUT ::
87 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
93 To build, save output files in a separate directory with O= ::
97 To build, save output files in a separate directory with KBUILD_OUTPUT ::
106 $ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests
117 See the top-level tools/testing/selftests/Makefile for the list of all
120 Running the full range hotplug selftests
125 $ make -C tools/testing/selftests hotplug
129 $ make -C tools/testing/selftests run_hotplug
143 $ make -C tools/testing/selftests install
147 $ make -C tools/testing/selftests install INSTALL_PATH=/some/other/path
161 To see the list of available tests, the `-l` option can be used::
163 $ ./run_kselftest.sh -l
165 The `-c` option can be used to run all the tests from a test collection, or
166 the `-t` option for specific single tests. Either can be used multiple times::
168 $ ./run_kselftest.sh -c bpf -c seccomp -t timers:posix_timers -t timer:nanosleep
170 For other features see the script usage output, seen with the `-h` option.
184 use a greater or lower timeout on the command line as with the `-o` or
185 the `--override-timeout` argument. For example to use 165 seconds instead
188 $ ./run_kselftest.sh --override-timeout 165
190 You can look at the TAP output to see if you ran into the timeout. Test
200 $ make -C tools/testing/selftests gen_tar
202 This generates a tarball in the `INSTALL_PATH/kselftest-packages` directory. By
204 specifying a `FORMAT` make variable. Any value recognized by `tar's auto-compress`_
207 $ make -C tools/testing/selftests gen_tar FORMAT=.xz
213 $ make -C tools/testing/selftests gen_tar TARGETS="bpf" FORMAT=.xz
215 .. _tar's auto-compress: https://www.gnu.org/software/tar/manual/html_node/gzip.html#auto_002dcompr…
228 * Don't cause the top-level "make run_tests" to fail if your feature is
248 TEST_CUSTOM_PROGS should be used by tests that require custom build
268 copying the files to the output directory
279 * If a test needs specific kernel config options enabled, add a config file in
282 e.g: tools/testing/selftests/android/config
293 kselftest-{all,install,clean,gen_tar}
294 kselftest-{all,install,clean,gen_tar} O=abo_path
295 kselftest-{all,install,clean,gen_tar} O=rel_path
296 make -C tools/testing/selftests {all,install,clean,gen_tar}
297 make -C tools/testing/selftests {all,install,clean,gen_tar} O=abs_path
298 make -C tools/testing/selftests {all,install,clean,gen_tar} O=rel_path
310 - ``tools/testing/selftests/kselftest_module.h``
311 - ``tools/testing/selftests/kselftest/module.sh``
318 kernel, but in cases where a non-test module is loaded, TEST_TAINT can be
322 ----------
332 3. Add line to config file e.g. ``tools/testing/selftests/lib/config``
338 .. code-block:: sh
342 make kselftest-merge
348 --------------
352 .. code-block:: c
354 // SPDX-License-Identifier: GPL-2.0+
382 -------------------
384 .. code-block:: sh
387 # SPDX-License-Identifier: GPL-2.0+
402 -------
404 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
409 -------
411 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
417 ---------
419 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h
422 .. kernel-doc:: tools/testing/selftests/kselftest_harness.h