| /Linux-v5.15/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 …]
|
| D | testing-overview.rst | 4 Kernel Testing Guide
8 There are a number of different tools for testing the Linux kernel, so knowing
29 for "white box" testing: because test code is part of the kernel, it can access
34 concept of 'unit' testing.
62 details. This aligns well with 'system' or 'end-to-end' testing.
74 Documentation/dev-tools/gcov.rst is GCC's coverage testing tool, which can be
|
| D | index.rst | 10 A brief overview of testing-specific tools can be found in
11 Documentation/dev-tools/testing-overview.rst
20 testing-overview
|
| /Linux-v5.15/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.15/Documentation/dev-tools/kunit/ |
| D | kunit-tool.rst | 10 kunit_tool is a script (``tools/testing/kunit/kunit.py``) that aids in building
43 ./tools/testing/kunit/kunit.py run
49 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
59 testing a particular subsystem), you can pass it as an option.
63 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
69 ./tools/testing/kunit/kunit.py run --help
82 ./tools/testing/kunit/kunit.py config
89 ./tools/testing/kunit/kunit.py build
96 ./tools/testing/kunit/kunit.py exec
115 ./tools/testing/kunit/kunit.py run --raw_output
[all …]
|
| D | index.rst | 4 KUnit - Unit Testing for the Linux Kernel
22 KUnit is a lightweight unit testing and mocking framework for the Linux kernel.
46 name. A unit test should be the finest granularity of testing and as such should
69 changes the way you go about testing and even writing code in the first place.
79 but this point also applies to testing. If your tests are slow, unreliable, are
95 * Documentation/dev-tools/kunit/api/index.rst - 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 | running_tips.rst | 18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run $@ )
36 $ ./tools/testing/kunit/kunit.py run 'sysctl*'
57 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
90 $ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
119 $ ./tools/testing/kunit/kunit.py run
132 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
144 the kernel, run the ``./linux`` binary), this section will focus on testing
214 $ ./tools/testing/kunit/kunit.py parse /var/log/dmesg
|
| 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 | usage.rst | 10 some basic knowledge of testing.
18 This document is organized into two main sections: Testing and Common Patterns.
20 second covers common testing patterns, e.g. how to isolate code and make it
23 Testing chapter
29 "K" is short for "kernel" so "KUnit" is the "(Linux) Kernel Unit Testing
32 a secondary goal. KUnit has no ambition of being the only testing framework for
33 the kernel; for example, it does not intend to be an end-to-end testing
36 What is Unit Testing?
137 Notice how it is immediately obvious what all the properties that we are testing
180 related tests most unit testing frameworks - including KUnit - provide the
[all …]
|
| /Linux-v5.15/tools/perf/tests/ |
| D | pmu-events.c | 259 pr_debug2("testing event e1 %s: mismatched desc, %s vs %s\n", in compare_pmu_events()
265 pr_debug2("testing event e1 %s: mismatched topic, %s vs %s\n", in compare_pmu_events()
271 pr_debug2("testing event e1 %s: mismatched long_desc, %s vs %s\n", in compare_pmu_events()
277 pr_debug2("testing event e1 %s: mismatched unit, %s vs %s\n", in compare_pmu_events()
283 pr_debug2("testing event e1 %s: mismatched perpkg, %s vs %s\n", in compare_pmu_events()
289 pr_debug2("testing event e1 %s: mismatched metric_expr, %s vs %s\n", in compare_pmu_events()
295 pr_debug2("testing event e1 %s: mismatched metric_name, %s vs %s\n", in compare_pmu_events()
301 pr_debug2("testing event e1 %s: mismatched deprecated, %s vs %s\n", in compare_pmu_events()
307 pr_debug2("testing event e1 %s: mismatched pmu string, %s vs %s\n", in compare_pmu_events()
313 pr_debug2("testing event e1 %s: mismatched compat string, %s vs %s\n", in compare_pmu_events()
[all …]
|
| /Linux-v5.15/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.15/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.15/lib/ |
| D | Kconfig.kfence | 19 Note that, KFENCE is not a substitute for explicit testing with tools
60 int "Stress testing of fault handling and error reporting" if EXPERT
66 and allocations/frees. A value of 0 disables stress testing logic.
68 Only for KFENCE testing; set to 0 if you are not a KFENCE developer.
75 Test suite for KFENCE, testing various error detection scenarios with
|
| /Linux-v5.15/tools/testing/selftests/bpf/progs/ |
| D | xdp_redirect_multi_kern.c | 14 /* One map use devmap, another one use devmap_hash for testing */
53 /* Using IPv4 for (BPF_F_BROADCAST | BPF_F_EXCLUDE_INGRESS) testing */ in xdp_redirect_map_multi_prog()
57 /* Using IPv6 for none flag testing */ in xdp_redirect_map_multi_prog()
60 /* All others for BPF_F_BROADCAST testing */ in xdp_redirect_map_multi_prog()
65 /* The following 2 progs are for 2nd devmap prog testing */
|
| /Linux-v5.15/tools/testing/selftests/rcutorture/bin/ |
| D | torture.sh | 16 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
320 amcdir="tools/testing/selftests/rcutorture/res/$ds/allmodconfig"
342 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…
348 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…
354 …torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --d…
366 …torture_set "refscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture refscale --al…
378 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…
384 …torture_set "rcuscale-kvfree" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --a…
390 …torture_set "clocksourcewd-1" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…
393 …torture_set "clocksourcewd-2" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…
[all …]
|
| /Linux-v5.15/tools/testing/selftests/kvm/ |
| D | kvm_page_table_test.c | 9 * use hugepages to back the guest memory for testing.
27 /* Default size(1GB) of the memory for testing */
83 * Guest physical memory offset of the testing memory slot.
90 * Guest virtual memory offset of the testing memory slot.
274 /* Align down GPA of the testing memslot */ in pre_init_before_test()
305 /* Do mapping(GVA->GPA) for the testing memory slot */ in pre_init_before_test()
324 pr_info("Testing guest mode: %s\n", vm_guest_mode_string(mode)); in pre_init_before_test()
325 pr_info("Testing memory backing src type: %s\n", in pre_init_before_test()
327 pr_info("Testing memory backing src granularity: 0x%lx\n", in pre_init_before_test()
329 pr_info("Testing memory size(aligned): 0x%lx\n", test_mem_size); in pre_init_before_test()
[all …]
|
| /Linux-v5.15/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 | 134 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding
135 userspace code in `tools/testing/selftests/bpf/prog_tests/test_lsm.c`_
140 .. _tools/testing/selftests/bpf/progs/lsm.c:
141 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
142 .. _tools/testing/selftests/bpf/prog_tests/test_lsm.c:
143 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
|
| /Linux-v5.15/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.15/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..."
|
| /Linux-v5.15/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.15/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.15/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.15/tools/testing/kunit/ |
| D | kunit_tool_test.py | 4 # A collection of tests for tools/testing/kunit/kunit.py
360 self.print_mock.assert_any_call(StrContains('Testing complete.'))
368 self.print_mock.assert_any_call(StrContains('Testing complete.'))
390 self.assertNotEqual(call, mock.call(StrContains('Testing complete.')))
399 self.assertNotEqual(call, mock.call(StrContains('Testing complete.')))
408 self.assertNotEqual(call, mock.call(StrContains('Testing complete.')))
424 self.print_mock.assert_any_call(StrContains('Testing complete.'))
432 self.print_mock.assert_any_call(StrContains('Testing complete.'))
440 self.print_mock.assert_any_call(StrContains('Testing complete.'))
457 self.print_mock.assert_any_call(StrContains('Testing complete.'))
[all …]
|
