Searched full:testing (Results 1 – 25 of 389) sorted by relevance
12345678910>>...16
| /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 …]
|
| D | index.rst | 10 A brief overview of testing-specific tools can be found in
11 Documentation/dev-tools/testing-overview.rst
17 testing-overview
|
| 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
123 In addition to testing a running kernel, one can also analyze kernel source code
|
| /Documentation/dev-tools/kunit/ |
| D | index.rst | 4 KUnit - Linux Kernel Unit Testing
30 This section details the kernel unit testing framework.
35 KUnit (Kernel unit testing framework) provides a common framework for
42 (C++ unit testing framework).
51 KUnit follows the white-box testing approach. The test has access to
55 In addition, KUnit has kunit_tool, a script (``tools/testing/kunit/kunit.py``)
74 Unit Testing
78 granularity of testing and allows all possible code paths to be tested in the
97 Unit Testing Advantages
100 - 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
|
| 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*'
43 $ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*'
64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
71 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
97 $ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
126 …$ ./tools/testing/kunit/kunit.py run --kunitconfig=.kunit/ --kunitconfig=tools/testing/kunit/confi…
139 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
147 …$ ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --kunitconfig=.kunit/ --kunitconfig=too…
162 the kernel, run the ``./linux`` binary), this section will focus on testing
[all …]
|
| D | style.rst | 11 automatically by testing systems.
44 unless we are actually testing other tests or the kunit framework itself. For
99 Part of the ``ext4`` subsystem, testing the ``inode`` area.
101 Part of the ``kunit`` implementation itself, testing the ``try_catch`` area.
103 Part of the ``apparmor`` subsystem, testing the ``property_entry`` area.
128 Tests should be named after what they are testing. This is often the name of the
162 tested, or be under [Kernel Hacking]->[Kernel Testing and Coverage]
|
| /Documentation/rust/ |
| D | testing.rst | 3 Testing title
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.
37 Kernel hacking -> Kernel Testing and Coverage -> KUnit - Enable support for unit tests
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
140 Kselftests are also available in the ``tools/testing/selftests/rust`` folder.
143 ``tools/testing/selftests/rust/config`` file and can be included with the aid
146 ./scripts/kconfig/merge_config.sh .config tools/testing/selftests/rust/config
|
| /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
|
| /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 | 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/…
|
| 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
|
| /Documentation/driver-api/rapidio/ |
| D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /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
92 How to enable automated testing on your tree
137 For testing changes to the scripts in the drm-ci repo, change the
143 How to incorporate external fixes in your testing
146 Often, regressions in other trees will prevent testing changes local to the
155 How to deal with automated testing labs that may be down
|
| /Documentation/translations/zh_CN/dev-tools/ |
| D | index.rst | 15 Documentation/translations/zh_CN/dev-tools/testing-overview.rst
21 testing-overview
|
| /Documentation/admin-guide/ |
| D | abi-testing.rst | 1 ABI testing symbols
19 .. kernel-abi:: ABI/testing
|
| /Documentation/translations/zh_TW/dev-tools/ |
| D | index.rst | 17 Documentation/translations/zh_TW/dev-tools/testing-overview.rst
26 testing-overview
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | checktransupdate.rst | 39 - ``./scripts/checktransupdate.py Documentation/translations/zh_CN/dev-tools/testing-overview.rst``
49 Documentation/translations/zh_CN/dev-tools/testing-overview.rst
|
| /Documentation/dev-tools/kunit/api/ |
| D | index.rst | 17 This page documents the KUnit kernel testing API. It is divided into the
25 - Documents all of the standard testing API
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-mockup.rst | 3 GPIO Testing Driver
14 The GPIO Testing Driver (gpio-mockup) provides a way to create simulated GPIO
15 chips for testing purposes. The lines exposed by these chips can be accessed
|
| /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 …]
|
| /Documentation/power/ |
| D | drivers-testing.rst | 2 Testing suspend and resume support in device drivers
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
24 2. Testing the driver
|
12345678910>>...16