| /linux-6.15/drivers/gpu/drm/ci/ |
| H A 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
114 alpine-build-testing:
146 debian-build-testing:
174 debian-testing:
178 debian-testing-asan:
[all …]
|
| H A D | test.yml | 25 - testing:arm32
31 - testing:arm32
42 - testing:arm64
48 - testing:arm64
59 - testing:x86_64
65 - testing:x86_64
86 - job: testing:arm64
462 - testing:x86_64
485 - testing:x86_64
|
| /linux-6.15/Documentation/dev-tools/ |
| H A D | kselftest.rst | 41 testing-devices
49 $ make -C tools/testing/selftests
53 $ make -C tools/testing/selftests run_tests
134 $ make -C tools/testing/selftests hotplug
138 $ make -C tools/testing/selftests run_hotplug
152 $ make -C tools/testing/selftests install
209 $ make -C tools/testing/selftests gen_tar
302 e.g: tools/testing/selftests/android/config
330 - ``tools/testing/selftests/kselftest_module.h``
383 * Kernel module for testing the foobinator
[all …]
|
| H A 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-6.15/tools/testing/selftests/net/rds/ |
| H A D | README.txt | 18 -d Log directory. Defaults to tools/testing/selftests/net/rds/rds_logs
29 tools/testing/selftests/net/rds/config.sh -g
32 tools/testing/selftests/net/rds/config.sh
35 vng --build --config tools/testing/selftests/net/config
39 "export PYTHONPATH=tools/testing/selftests/net/; tools/testing/selftests/net/rds/run.sh"
41 An HTML coverage report will be output in tools/testing/selftests/net/rds/rds_logs/coverage/.
|
| /linux-6.15/Documentation/dev-tools/kunit/ |
| H A D | index.rst | 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``)
69 granularity of testing and allows all possible code paths to be tested in the
91 - Increases testing speed and development in the long run.
93 compared to acceptance testing.
106 or to experiment with tools/testing/kunit/kunit.py and the example test under
109 Happy testing!
|
| H A D | run_wrapper.rst | 19 ./tools/testing/kunit/kunit.py run
59 ./tools/testing/kunit/kunit.py run --help
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
153 dmesg | ./tools/testing/kunit/kunit.py parse
201 ./tools/testing/kunit/kunit.py run --arch=x86_64
208 ./tools/testing/kunit/kunit.py run \
219 ``tools/testing/kunit/qemu_configs/x86_64.py``.
[all …]
|
| H A 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``
|
| /linux-6.15/tools/testing/selftests/rcutorture/bin/ |
| H A D | torture.sh | 432 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…
438 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…
453 …torture_set "rcurttorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$du…
457 …torture_set "rcurttorture-exp" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration …
463 …tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh --datestamp "$ds/results-srcu-lockdep" > $T…
540 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…
568 …torture_set "rcuscale-$prim$torture_suffix" tools/testing/selftests/rcutorture/bin/kvm-again.sh "`…
584 …torture_set "clocksourcewd-1" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…
587 …torture_set "clocksourcewd-2" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…
593 …torture_set "clocksourcewd-3" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 4…
[all …]
|
| /linux-6.15/tools/testing/kunit/configs/ |
| H A 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-6.15/tools/testing/selftests/rcutorture/doc/ |
| H A 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-6.15/Documentation/bpf/ |
| H A 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…
495 .. _`tools/testing/selftests/bpf/test_sockmap.c`: https://git.kernel.org/pub/scm/linux/kernel/git/t…
[all …]
|
| H A 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-6.15/Documentation/ABI/testing/ |
| H A 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-6.15/drivers/net/wireless/virtual/ |
| H A D | Kconfig | 2 tristate "Simulated radio testing tool for mac80211"
5 This driver is a developer testing tool that can be used to test
7 needed for normal wireless LAN usage and is only for testing. See
|
| /linux-6.15/Documentation/translations/zh_CN/security/ |
| H A D | landlock.rst | 87 找到：tools/testing/selftests/landlock/
121 .. _tools/testing/selftests/landlock/:
123 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/landl…
|
| /linux-6.15/drivers/thermal/testing/ |
| H A D | Makefile | 5 obj-$(CONFIG_THERMAL_CORE_TESTING) += thermal-testing.o
7 thermal-testing-y := command.o zone.o
|
| /linux-6.15/Documentation/driver-api/rapidio/ |
| H A D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /linux-6.15/Documentation/rust/ |
| H A D | testing.rst | 27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
32 built-in vs. command line testing.
73 testing facilities. For instance, the kernel log would look like::
117 require passing context, unlike those for KUnit testing (i.e.
119 documentation do not need to care about which testing framework is used. In
147 Kselftests are also available in the ``tools/testing/selftests/rust`` folder.
150 ``tools/testing/selftests/rust/config`` file and can be included with the aid
153 ./scripts/kconfig/merge_config.sh .config tools/testing/selftests/rust/config
|
| /linux-6.15/Documentation/gpu/ |
| H A 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
98 How to enable automated testing on your tree
143 For testing changes to the scripts in the drm-ci repo, change the
149 How to incorporate external fixes in your testing
152 Often, regressions in other trees will prevent testing changes local to the
161 How to deal with automated testing labs that may be down
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | abi.rst | 16 abi-testing
27 abi-testing-files
|
| /linux-6.15/Documentation/translations/zh_CN/dev-tools/ |
| H A D | index.rst | 15 Documentation/translations/zh_CN/dev-tools/testing-overview.rst
21 testing-overview
|
| /linux-6.15/Documentation/translations/zh_TW/dev-tools/ |
| H A D | index.rst | 17 Documentation/translations/zh_TW/dev-tools/testing-overview.rst
26 testing-overview
|
| /linux-6.15/drivers/media/test-drivers/vivid/ |
| H A D | Kconfig | 18 It is highly configurable and is ideal for testing applications.
34 bool "Enable Framebuffer for testing Output Overlay"
41 testing Output Overlay.
|
| /linux-6.15/lib/ |
| H A 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
|