| /Linux-v6.6/Documentation/dev-tools/ |
| D | kselftest.rst | 5 The kernel contains a set of "self tests" under the tools/testing/selftests/
40 $ make -C tools/testing/selftests
44 $ make -C tools/testing/selftests run_tests
87 $ make -C tools/testing/selftests TARGETS=ptrace run_tests
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
125 $ make -C tools/testing/selftests hotplug
129 $ make -C tools/testing/selftests run_hotplug
138 tool) to install selftests in the default location (`tools/testing/selftests/kselftest_install`),
143 $ make -C tools/testing/selftests install
[all …]
|
| /Linux-v6.6/Documentation/dev-tools/kunit/ |
| D | index.rst | 4 KUnit - Linux Kernel Unit Testing
21 This section details the kernel unit testing framework.
26 KUnit (Kernel unit testing framework) provides a common framework for
33 (C++ unit testing framework).
42 KUnit follows the white-box testing approach. The test has access to
46 In addition, KUnit has kunit_tool, a script (``tools/testing/kunit/kunit.py``)
65 Unit Testing
69 granularity of testing and allows all possible code paths to be tested in the
88 Unit Testing Advantages
91 - Increases testing speed and development in the long run.
[all …]
|
| D | run_wrapper.rst | 19 ./tools/testing/kunit/kunit.py run
33 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all`
53 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig
59 ./tools/testing/kunit/kunit.py run --help
67 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/kunit/configs…
81 cp tools/testing/kunit/configs/default.config .kunit/.kunitconfig
111 ./tools/testing/kunit/kunit.py config
118 ./tools/testing/kunit/kunit.py build
126 ./tools/testing/kunit/kunit.py exec
141 ./tools/testing/kunit/kunit.py run --raw_output
[all …]
|
| D | faq.rst | 9 KUnit is a unit testing framework. Autotest, kselftest (and some others) are
14 test should be the finest granularity of testing and should allow all possible
19 There are no testing frameworks currently available for the kernel that do not
21 testing frameworks require tests to be written in userspace and run on the
23 disqualifying any of them from being considered unit testing frameworks.
34 (``tools/testing/kunit/kunit.py``) that might not support some architectures
50 test should be the finest granularity of testing and, as such, allows all
73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
|
| D | architecture.rst | 9 - `In-Kernel Testing Framework`_
12 In-Kernel Testing Framework
15 The kernel testing library supports KUnit tests written in C using
114 In the event of a failure, the testing flow differs as follows:
159 ``kunit_tool`` is a Python script, found in ``tools/testing/kunit/kunit.py``. It
170 (for example, ``tools/testing/kunit/qemu configs/powerpc.py``) contains
180 ``./tools/testing/kunit/kunit.py config`` and
186 ``build`` argument: ``./tools/testing/kunit/kunit.py build``.
193 argument: ``./tools/testing/kunit/kunit.py exec``.
|
| D | start.rst | 24 ./tools/testing/kunit/kunit.py run
77 tools/testing/kunit/kunit.py config
99 ./tools/testing/kunit/kunit.py run \
105 ./tools/testing/kunit/kunit.py run \
135 ./tools/testing/kunit/kunit.py run "kunit_executor_test"
140 ./tools/testing/kunit/kunit.py run "example.example_simple_test"
146 ./tools/testing/kunit/kunit.py run "*.*64*"
164 option (under Kernel Hacking/Kernel Testing and Coverage in
284 ./tools/testing/kunit/kunit.py run
309 for testing different things), see Documentation/dev-tools/kunit/usage.rst
|
| /Linux-v6.6/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-v6.6/Documentation/bpf/ |
| D | map_sockmap.rst | 348 - `tools/testing/selftests/bpf/progs/test_sockmap_kern.h`_
349 - `tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`_
350 - `tools/testing/selftests/bpf/progs/sockmap_verdict_prog.c`_
351 - `tools/testing/selftests/bpf/progs/test_sockmap_listen.c`_
352 - `tools/testing/selftests/bpf/progs/test_sockmap_update.c`_
439 - `tools/testing/selftests/bpf/prog_tests/sockmap_basic.c`_
440 - `tools/testing/selftests/bpf/test_sockmap.c`_
441 - `tools/testing/selftests/bpf/test_maps.c`_
491 … _`tools/testing/selftests/bpf/progs/test_sockmap_kern.h`: https://git.kernel.org/pub/scm/linux/ke…
492 …_`tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`: https://git.kernel.org/pub/scm/linux/ke…
[all …]
|
| 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 | prog_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-v6.6/tools/perf/tests/ |
| D | pmu-events.c | 288 pr_debug2("testing event e1 %s: mismatched name string, %s vs %s\n", in compare_pmu_events()
294 pr_debug2("testing event e1 %s: mismatched compat string, %s vs %s\n", in compare_pmu_events()
300 pr_debug2("testing event e1 %s: mismatched event, %s vs %s\n", in compare_pmu_events()
306 pr_debug2("testing event e1 %s: mismatched desc, %s vs %s\n", in compare_pmu_events()
312 pr_debug2("testing event e1 %s: mismatched topic, %s vs %s\n", in compare_pmu_events()
318 pr_debug2("testing event e1 %s: mismatched long_desc, %s vs %s\n", in compare_pmu_events()
324 pr_debug2("testing event e1 %s: mismatched pmu string, %s vs %s\n", in compare_pmu_events()
330 pr_debug2("testing event e1 %s: mismatched unit, %s vs %s\n", in compare_pmu_events()
336 pr_debug2("testing event e1 %s: mismatched perpkg, %d vs %d\n", in compare_pmu_events()
342 pr_debug2("testing event e1 %s: mismatched deprecated, %d vs %d\n", in compare_pmu_events()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/powerpc/mm/ |
| D | exec_prot.c | 172 printf("Testing read on --x, should fault..."); in test()
184 printf("Testing write on --x, should fault..."); in test()
190 printf("Testing exec on ---, should fault..."); in test()
194 printf("Testing exec on r--, should fault..."); in test()
198 printf("Testing exec on -w-, should fault..."); in test()
202 printf("Testing exec on rw-, should fault..."); in test()
206 printf("Testing exec on --x, should succeed..."); in test()
210 printf("Testing exec on r-x, should succeed..."); in test()
214 printf("Testing exec on -wx, should succeed..."); in test()
218 printf("Testing exec on rwx, should succeed..."); in test()
|
| /Linux-v6.6/drivers/gpu/drm/ci/ |
| D | build.yml | 43 # Build IGT for testing on devices
60 # Build kernels for testing on devices
62 testing:arm32:
74 testing:arm64:
86 testing:x86_64:
99 # Jobs for build-testing different configurations
|
| D | test.yml | 28 - testing:arm32
33 - testing:arm32
43 - testing:arm64
48 - testing:arm64
58 - testing:x86_64
63 - testing:x86_64
79 - job: testing:arm64
331 - testing:x86_64
|
| /Linux-v6.6/tools/testing/selftests/rcutorture/bin/ |
| D | torture.sh | 16 RCUTORTURE="`pwd`/tools/testing/selftests/rcutorture"; export RCUTORTURE
345 amcdir="tools/testing/selftests/rcutorture/res/$ds/allmodconfig"
382 rtfdir="tools/testing/selftests/rcutorture/res/$ds/results-rcutasksflavors"
394 …tools/testing/selftests/rcutorture/bin/kvm.sh --datestamp "$ds/results-rcutasksflavors/$flavor" --…
416 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…
422 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…
430 …torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --d…
437 …torture_set "rcurttorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$du…
441 …torture_set "rcurttorture-exp" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration …
447 …tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh --datestamp "$ds/results-srcu-lockdep" > $T…
[all …]
|
| /Linux-v6.6/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-v6.6/Documentation/gpu/ |
| D | automated_testing.rst | 4 Automated testing of the DRM subsystem
13 testing to have to acquire and maintain what can be a considerable amount of
21 can be used as well for testing the DRM subsystem. This document explains how
22 people interested in testing it can use this shared infrastructure to save
78 How to enable automated testing on your tree
120 For testing changes to the scripts in the drm-ci repo, change the
126 How to incorporate external fixes in your testing
129 Often, regressions in other trees will prevent testing changes local to the
138 How to deal with automated testing labs that may be down
|
| /Linux-v6.6/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-v6.6/tools/perf/tests/shell/ |
| D | lock_contention.sh | 39 echo "Testing perf lock record and perf lock contention"
52 echo "Testing perf lock contention --use-bpf"
70 echo "Testing perf lock record and perf lock contention at the same time"
82 echo "Testing perf lock contention --threads"
105 echo "Testing perf lock contention --lock-addr"
128 echo "Testing perf lock contention --type-filter (w/ spinlock)"
150 echo "Testing perf lock contention --lock-filter (w/ tasklist_lock)"
182 echo "Testing perf lock contention --callstack-filter (w/ unix_stream)"
210 echo "Testing perf lock contention --callstack-filter with task aggregation"
238 echo "Testing perf lock contention CSV output"
|
| /Linux-v6.6/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-v6.6/lib/ |
| D | Kconfig.kfence | 19 Note that, KFENCE is not a substitute for explicit testing with tools
76 int "Stress testing of fault handling and error reporting" if EXPERT
82 and allocations/frees. A value of 0 disables stress testing logic.
84 Only for KFENCE testing; set to 0 if you are not a KFENCE developer.
91 Test suite for KFENCE, testing various error detection scenarios with
|
| /Linux-v6.6/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 */
78 * Guest physical memory offset of the testing memory slot.
85 * Guest virtual memory offset of the testing memory slot.
260 /* Align down GPA of the testing memslot */ in pre_init_before_test()
285 /* Do mapping(GVA->GPA) for the testing memory slot */ in pre_init_before_test()
303 pr_info("Testing guest mode: %s\n", vm_guest_mode_string(mode)); in pre_init_before_test()
304 pr_info("Testing memory backing src type: %s\n", in pre_init_before_test()
306 pr_info("Testing memory backing src granularity: 0x%lx\n", in pre_init_before_test()
308 pr_info("Testing memory size(aligned): 0x%lx\n", test_mem_size); in pre_init_before_test()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/bpf/ |
| D | test_flow_dissector.sh | 25 echo "Testing global flow dissector..."
108 echo "Testing IPv4..."
120 echo "Testing IPv4 from 127.0.0.127 (fallback to generic dissector)..."
128 echo "Testing IPIP..."
139 echo "Testing IPv4 + GRE..."
152 echo "Testing port range..."
166 echo "Testing IPv6..."
|
| /Linux-v6.6/tools/testing/kunit/configs/ |
| D | coverage_uml.config | 4 # ./tools/testing/kunit/kunit.py run \
5 # --kunitconfig=tools/testing/kunit/configs/all_tests_uml.config \
6 # --kunitconfig=tools/testing/kunit/configs/coverage_uml.config
|
| /Linux-v6.6/Documentation/RCU/ |
| D | torture.rst | 83 an RCU priority inversion condition. If you are testing RCU
166 Therefore, the tools/testing/selftests/rcutorture/bin/kvm.sh
167 script is available for mainline testing for x86, arm64, and
169 tools/testing/selftests/rcutorture/configs/rcu/CFLIST, with each test
175 On larger systems, rcutorture testing can be accelerated by passing the
244 tools/testing/selftests/rcutorture/res in timestamped directories. A
248 tools/testing/selftests/rcutorture/bin/kvm-find-errors.sh \
249 tools/testing/selftests/rcutorture/res/2020.01.20-15.54.23
319 tools/testing/selftests/rcutorture/res/2022.11.03-11.26.28
323 kvm-again.sh tools/testing/selftests/rcutorture/res/2022.11.03-11.26.28
[all …]
|
