| /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/tools/hv/ |
| D | vmbus_testing | 7 # 1. delay testing
25 # in /drivers/hv/debugfs.c. All fuzz testing
137 # display Testing status of single device
163 # display Testing state of devices
168 print("Testing = ON for: {}"
171 print("Testing = OFF for: {}"
202 # set testing state of device
208 print("Testing = ON for device: {}"
212 print("Testing = OFF for device: {}"
215 # get testing state of device
[all …]
|
| /Linux-v5.10/tools/perf/tests/ |
| D | pmu-events.c | 183 pr_debug2("testing event table %s: mismatched desc, %s vs %s\n", in test_pmu_event_table()
189 pr_debug2("testing event table %s: mismatched topic, %s vs %s\n", in test_pmu_event_table()
196 pr_debug2("testing event table %s: mismatched long_desc, %s vs %s\n", in test_pmu_event_table()
203 pr_debug2("testing event table %s: mismatched unit, %s vs %s\n", in test_pmu_event_table()
210 pr_debug2("testing event table %s: mismatched perpkg, %s vs %s\n", in test_pmu_event_table()
217 pr_debug2("testing event table %s: mismatched metric_expr, %s vs %s\n", in test_pmu_event_table()
224 pr_debug2("testing event table %s: mismatched metric_name, %s vs %s\n", in test_pmu_event_table()
231 pr_debug2("testing event table %s: mismatched deprecated, %s vs %s\n", in test_pmu_event_table()
237 pr_debug("testing event table %s: pass\n", table->name); in test_pmu_event_table()
241 pr_err("testing event table: could not find event %s\n", in test_pmu_event_table()
[all …]
|
| /Linux-v5.10/kernel/ |
| D | backtracetest.c | 18 pr_info("Testing a backtrace from process context.\n"); in backtrace_test_normal()
36 pr_info("Testing a backtrace from irq context.\n"); in backtrace_test_irq()
50 pr_info("Testing a saved backtrace.\n"); in backtrace_test_saved()
65 pr_info("====[ backtrace testing ]===========\n"); in backtrace_regression_test()
71 pr_info("====[ end of backtrace testing ]====\n"); in backtrace_regression_test()
|
| /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.
|
| /Linux-v5.10/Documentation/dev-tools/kunit/ |
| D | index.rst | 4 KUnit - Unit Testing for the Linux Kernel
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 | 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 | 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
165 tested, or be under [Kernel Hacking]→[Kernel Testing and Coverage]
|
| 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
|
| /Linux-v5.10/Documentation/bpf/ |
| D | s390.rst | 2 Testing BPF on s390
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
|
| 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/…
|
| /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/bpf/ |
| D | test_flow_dissector.sh | 23 echo "Testing global flow dissector..."
106 echo "Testing IPv4..."
118 echo "Testing IPIP..."
129 echo "Testing IPv4 + GRE..."
142 echo "Testing port range..."
156 echo "Testing IPv6..."
|
| D | test_tunnel.sh | 701 echo "Testing GRE tunnel..."
705 echo "Testing IP6GRE tunnel..."
709 echo "Testing IP6GRETAP tunnel..."
713 echo "Testing ERSPAN tunnel..."
717 echo "Testing IP6ERSPAN tunnel..."
721 echo "Testing VXLAN tunnel..."
725 echo "Testing IP6VXLAN tunnel..."
729 echo "Testing GENEVE tunnel..."
733 echo "Testing IP6GENEVE tunnel..."
737 echo "Testing IPIP tunnel..."
[all …]
|
| /Linux-v5.10/Documentation/usb/ |
| D | gadget-testing.rst | 2 Gadget Testing
5 This file summarizes information on basic testing of USB functions
50 Testing the ACM function
98 Testing the ECM function
138 Testing the ECM subset function
178 Testing the EEM function
208 Testing the FFS function
248 Testing the HID function
281 Testing the LOOPBACK function
338 Testing the MASS STORAGE function
[all …]
|
| /Linux-v5.10/tools/testing/selftests/kvm/include/ |
| D | perf_test_util.h | 3 * tools/testing/selftests/kvm/include/perf_test_util.h
27 * Guest physical memory offset of the testing memory slot.
34 * Guest virtual memory offset of the testing memory slot.
114 pr_info("Testing guest mode: %s\n", vm_guest_mode_string(mode)); in create_vm()
157 /* Add an extra memory slot for testing */ in create_vm()
|
| /Linux-v5.10/tools/testing/selftests/sysctl/ |
| D | sysctl.sh | 223 echo "== Testing sysctl behavior against ${TARGET} =="
311 echo -n "Testing that $1 fails as expected..."
400 echo -n "Testing INT_MAX works ..."
413 echo -n "Testing INT_MAX + 1 will fail as expected..."
426 echo -n "Testing negative values will work as expected..."
442 echo -n "Testing array works as expected ... "
454 echo -n "Testing skipping trailing array elements works ... "
471 echo -n "Testing PAGE_SIZE limit on array works ... "
489 echo -n "Testing exceeding PAGE_SIZE limit fails as expected ... "
510 echo -n "Testing UINT_MAX works ..."
[all …]
|
| /Linux-v5.10/drivers/mtd/tests/ |
| D | speedtest.c | 245 pr_info("testing eraseblock write speed\n"); in mtd_speedtest_init()
263 pr_info("testing eraseblock read speed\n"); in mtd_speedtest_init()
285 pr_info("testing page write speed\n"); in mtd_speedtest_init()
303 pr_info("testing page read speed\n"); in mtd_speedtest_init()
325 pr_info("testing 2 page write speed\n"); in mtd_speedtest_init()
343 pr_info("testing 2 page read speed\n"); in mtd_speedtest_init()
361 pr_info("Testing erase speed\n"); in mtd_speedtest_init()
373 pr_info("Testing %dx multi-block erase speed\n", in mtd_speedtest_init()
|
| /Linux-v5.10/drivers/gpu/drm/radeon/ |
| D | radeon_test.c | 250 pr_warn("Error while testing BO move\n"); in radeon_do_test_moves()
403 pr_warn("Error while testing ring sync (%d)\n", r); in radeon_test_ring_sync()
513 pr_warn("Error while testing ring sync (%d)\n", r); in radeon_test_ring_sync2()
543 DRM_INFO("Testing syncing between rings %d and %d...\n", i, j); in radeon_test_syncing()
546 DRM_INFO("Testing syncing between rings %d and %d...\n", j, i); in radeon_test_syncing()
560 DRM_INFO("Testing syncing between rings %d, %d and %d...\n", i, j, k); in radeon_test_syncing()
563 DRM_INFO("Testing syncing between rings %d, %d and %d...\n", i, k, j); in radeon_test_syncing()
566 DRM_INFO("Testing syncing between rings %d, %d and %d...\n", j, i, k); in radeon_test_syncing()
569 DRM_INFO("Testing syncing between rings %d, %d and %d...\n", j, k, i); in radeon_test_syncing()
572 DRM_INFO("Testing syncing between rings %d, %d and %d...\n", k, i, j); in radeon_test_syncing()
[all …]
|
| /Linux-v5.10/tools/testing/kunit/ |
| D | kunit_tool_test.py | 4 # A collection of tests for tools/testing/kunit/kunit.py
320 self.print_mock.assert_any_call(StrContains('Testing complete.'))
328 self.print_mock.assert_any_call(StrContains('Testing complete.'))
352 assert kall != mock.call(StrContains('Testing complete.'))
361 assert kall != mock.call(StrContains('Testing complete.'))
368 self.print_mock.assert_any_call(StrContains('Testing complete.'))
376 self.print_mock.assert_any_call(StrContains('Testing complete.'))
384 self.print_mock.assert_any_call(StrContains('Testing complete.'))
400 self.print_mock.assert_any_call(StrContains('Testing complete.'))
|
| /Linux-v5.10/Documentation/fault-injection/ |
| 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/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/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/Documentation/admin-guide/gpio/ |
| D | gpio-mockup.rst | 3 GPIO Testing Driver
6 The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
7 chips for testing purposes. The lines exposed by these chips can be accessed
|
| /Linux-v5.10/drivers/staging/media/atomisp/pci/isp/kernels/hdr/ |
| D | ia_css_hdr_types.h | 25 * \detail Currently HDR parameters are used only for testing purposes
46 * \detail Currently HDR parameters are used only for testing purposes
54 * \detail Currently HDR parameters are used only for testing purposes
|
