Lines Matching full:run

7 paths in the kernel. Tests are intended to be run after building, installing
10 Kselftest from mainline can be run on older stable kernels. Running tests
11 from mainline offers the best coverage. Several test rings run mainline
14 able to run that test on an older kernel. Hence, it is important to keep
25 to run the full range of hot-plug tests. In default mode, hot-plug tests run
27 run on a single cpu as opposed to all hotplug capable cpus, and memory
28 hotplug test is run on 2% of hotplug capable memory instead of 10%.
30 kselftest runs as a userspace process.  Tests that can be written/run in
32 run in kernel space may wish to use a `Test Module`_.
34 Running the selftests (hotplug tests are run in limited mode)
42 To run the tests::
46 To build and run the tests with a single command, use::
69 The above commands by default run the tests and print full pass/fail report.
75 To run kselftest with summary option enabled ::
83 single test to run, or a list of tests to run.
85 To run only tests targeted for a single subsystem::
89 You can specify multiple tests to build and run::
104 To run all tests but a single subsystem::
112 You can also specify a restricted list of tests to run together with a
127 To run the hotplug tests::
153 is a script named `run_kselftest.sh` to run the tests.
155 You can simply do the following to run the installed Kselftests. Please
165 The `-c` option can be used to run all the tests from a test collection, or
182 expected time it takes to run a test. If you have control over the systems
183 which will run the tests you can configure a test runner on those systems to
191 runners which know a test must run under a specific time can then optionally
197 In some cases packaging is desired, such as when tests need to run on a
198 different system. To package selftests, run::
254    TEST_CUSTOM_PROGS and TEST_PROGS will be run by common run_tests.
317 2. Create the test script that will run (load/unload) the module