Searched refs:testing (Results 1 – 25 of 398) sorted by relevance
12345678910>>...16
| /Linux-v5.10/Documentation/dev-tools/ |
| D | kselftest.rst | 5 The kernel contains a set of "self tests" under the tools/testing/selftests/
31 $ make -C tools/testing/selftests
35 $ make -C tools/testing/selftests run_tests
78 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
97 $ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests
108 See the top-level tools/testing/selftests/Makefile for the list of all
116 $ make -C tools/testing/selftests hotplug
120 $ make -C tools/testing/selftests run_hotplug
129 tool) to install selftests in the default location (`tools/testing/selftests/kselftest_install`),
134 $ make -C tools/testing/selftests install
[all …]
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | debugfs-hyperv | 5 Description: Fuzz testing status of a vmbus device, whether its in an ON
13 Description: Fuzz testing buffer interrupt delay value between 0 - 1000
21 Description: Fuzz testing message delay value between 0 - 1000 microseconds
|
| /Linux-v5.10/tools/testing/selftests/rcutorture/doc/ |
| D | rcu-test-image.txt | 5 $ size tools/testing/selftests/rcutorture/initrd/init
7 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init
10 some aspect of the rcutorture testing. This will require a more fully
15 tools/testing/selftests/rcutorture/initrd
17 For example, your tools/testing/selftests/rcutorture/initrd/init might
19 scripts need starting to properly monitor or control your testing.
|
| D | initrd.txt | 4 tools/testing/selftests/rcutorture/bin/mkinitrd.sh.
11 cd tools/testing/selftests/rcutorture
|
| /Linux-v5.10/Documentation/driver-api/rapidio/ |
| D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /Linux-v5.10/Documentation/dev-tools/kunit/api/ |
| D | index.rst | 10 This section documents the KUnit kernel testing API. It is divided into the
14 :doc:`test` documents all of the standard testing API
|
| /Linux-v5.10/Documentation/dev-tools/kunit/ |
| D | kunit-tool.rst | 10 kunit_tool is a script (``tools/testing/kunit/kunit.py``) that aids in building
38 ./tools/testing/kunit/kunit.py run
44 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
57 ./tools/testing/kunit/kunit.py run --help
|
| D | faq.rst | 9 KUnit is a unit testing framework. Autotest, kselftest (and some others) are
14 the finest granularity of testing and as such should allow all possible code
19 There are no testing frameworks currently available for the kernel that do not
23 considered unit testing frameworks.
34 like the KUnit Wrapper (``tools/testing/kunit/kunit.py``) that does not support
48 name. A unit test should be the finest granularity of testing and as such
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
|
| D | index.rst | 20 KUnit is a lightweight unit testing and mocking framework for the Linux kernel.
44 name. A unit test should be the finest granularity of testing and as such should
67 changes the way you go about testing and even writing code in the first place.
77 but this point also applies to testing. If your tests are slow, unreliable, are
92 * :doc:`api/index` - for the list of KUnit APIs used for testing
|
| D | style.rst | 11 automatically by testing systems.
45 unless you are actually testing other tests or the kunit framework itself.
103 Part of the ``ext4`` subsystem, testing the ``inode`` area.
105 Part of the ``kunit`` implementation itself, testing the ``try_catch`` area.
107 Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
131 Tests should be named after what they're testing. This is often the name of the
|
| /Linux-v5.10/Documentation/bpf/ |
| D | bpf_lsm.rst | 133 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding
134 userspace code in `tools/testing/selftests/bpf/prog_tests/test_lsm.c`_
139 .. _tools/testing/selftests/bpf/progs/lsm.c:
140 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
141 .. _tools/testing/selftests/bpf/prog_tests/test_lsm.c:
142 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
|
| D | s390.rst | 29 testing \
97 testing \
122 -C tools/testing/selftests \
124 INSTALL_PATH=$PWD/tools/testing/selftests/kselftest_install \
162 cd /linux/tools/testing/selftests/kselftest_install
167 cd /linux/tools/testing/selftests/bpf
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | abi-testing.rst | 1 ABI testing symbols
19 .. kernel-abi:: $srctree/Documentation/ABI/testing
|
| D | abi.rst | 9 abi-testing
|
| /Linux-v5.10/tools/testing/selftests/arm64/ |
| D | README | 16 $ make -C tools/testing/selftests TARGETS=arm64 \
21 $ make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS="tags signal" \
|
| /Linux-v5.10/lib/kunit/ |
| D | Kconfig | 9 testing and mocking framework for the Linux kernel. These tests are
32 KUnit and test KUnit. This option should only be enabled for testing
33 purposes by developers interested in testing that KUnit works as
|
| /Linux-v5.10/Documentation/fault-injection/ |
| D | notifier-error-inject.rst | 91 There are tools/testing/selftests using the notifier error injection features
94 * tools/testing/selftests/cpu-hotplug/on-off-test.sh
95 * tools/testing/selftests/memory-hotplug/on-off-test.sh
|
| D | fault-injection.rst | 204 This feature is intended for systematic testing of faults in a single
366 tools/testing/fault-injection/failcmd.sh. Please run a command
367 "./tools/testing/fault-injection/failcmd.sh --help" for more information and
372 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab
375 # ./tools/testing/fault-injection/failcmd.sh \
376 -- make -C tools/testing/selftests/ run_tests
381 # ./tools/testing/fault-injection/failcmd.sh --times=100 \
382 -- make -C tools/testing/selftests/ run_tests
388 ./tools/testing/fault-injection/failcmd.sh --times=100 \
389 -- make -C tools/testing/selftests/ run_tests
|
| /Linux-v5.10/tools/ |
| D | Makefile | 88 $(call descend,testing/$@)
121 $(call descend,testing/$(@:_install=),install)
168 $(call descend,testing/$(@:_clean=),clean)
|
| /Linux-v5.10/Documentation/gpu/ |
| D | vkms.rst | 70 - Writeback connector. This is useful for testing compositors if you don't have
79 We already have vgem, which is a gem driver for testing rendering, similar to
80 how vkms is for testing the modeset side. Adding buffer sharing support to vkms
91 testing. Also needs support to specify the EDID.
|
| /Linux-v5.10/drivers/staging/media/imx/ |
| D | TODO | 28 - i.MX7: runtime testing with parallel sensor, links setup and streaming
30 - i.MX7: runtime testing with different formats, for the time only 10-bit bayer
|
| /Linux-v5.10/tools/testing/ktest/examples/ |
| D | README | 10 crosstests.conf - this config shows an example of testing a git repo against
17 used to perform real testing.
|
| /Linux-v5.10/Documentation/i2c/ |
| D | slave-testunit-backend.rst | 11 easy to obtain). Examples include multi-master testing, and SMBus Host Notify
12 testing. For some tests, the I2C slave controller must be able to switch
15 Note that this is a device for testing and debugging. It should not be enabled
|
| /Linux-v5.10/drivers/scsi/aacraid/ |
| D | TODO | 2 o More testing
|
| /Linux-v5.10/tools/testing/selftests/rcutorture/ |
| D | Makefile | 3 ( cd ../../../..; tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs TREE01 )
|
12345678910>>...16
