Searched refs:testing (Results  1 – 25 of 506) sorted by relevance
12345678910>>...21
| /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 …]
 
 | 
| D | index.rst | 10 A brief overview of testing-specific tools can be found in11 Documentation/dev-tools/testing-overview.rst
 20    testing-overview
 
 | 
| /Linux-v6.6/Documentation/dev-tools/kunit/ | 
| 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!
 
 | 
| D | run_wrapper.rst | 19 	./tools/testing/kunit/kunit.py run33 	./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) are14 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 | start.rst | 24 	./tools/testing/kunit/kunit.py run77 	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*"
 284 	./tools/testing/kunit/kunit.py run
 309 for testing different things), see Documentation/dev-tools/kunit/usage.rst
 
 | 
| D | architecture.rst | 15 The kernel testing library supports KUnit tests written in C using114   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``.
 
 | 
| /Linux-v6.6/tools/testing/selftests/rcutorture/bin/ | 
| D | torture.sh | 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…
 524 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…
 552 …torture_set "rcuscale-$prim$torture_suffix" tools/testing/selftests/rcutorture/bin/kvm-again.sh "`…
 562 …torture_set "rcuscale-kvfree" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --a…
 [all …]
 
 | 
| /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/tools/testing/selftests/rcutorture/doc/ | 
| D | rcu-test-image.txt | 5 $ size tools/testing/selftests/rcutorture/initrd/init7     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.
 
 | 
| D | initrd.txt | 4 tools/testing/selftests/rcutorture/bin/mkinitrd.sh.11 cd tools/testing/selftests/rcutorture
 
 | 
| /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 | prog_lsm.rst | 134 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding135 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 | 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
 
 | 
| /Linux-v6.6/Documentation/ABI/testing/ | 
| D | debugfs-hyperv | 5 Description:    Fuzz testing status of a vmbus device, whether its in an ON13 Description:    Fuzz testing buffer interrupt delay value between 0 - 1000
 21 Description:    Fuzz testing message delay value between 0 - 1000 microseconds
 
 | 
| /Linux-v6.6/drivers/net/wireless/virtual/ | 
| 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-v6.6/Documentation/gpu/ | 
| D | automated_testing.rst | 4 Automated testing of the DRM subsystem13 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/Documentation/driver-api/rapidio/ | 
| D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and7 Documentation/ABI/testing/sysfs-class-rapidio
 
 | 
| /Linux-v6.6/Documentation/translations/zh_CN/dev-tools/ | 
| D | index.rst | 15 Documentation/translations/zh_CN/dev-tools/testing-overview.rst24    testing-overview
 
 | 
| /Linux-v6.6/Documentation/dev-tools/kunit/api/ | 
| D | index.rst | 14 This page documents the KUnit kernel testing API. It is divided into the19  - Documents all of the standard testing API
 
 | 
| /Linux-v6.6/drivers/iommu/iommufd/ | 
| D | Kconfig | 29 	  purpose of testing IOMMUFD with unmodified userspace supporting VFIO33 	  Unless testing IOMMUFD, say N here.
 43 	  tools/testing/selftests/iommu
 
 | 
| /Linux-v6.6/lib/ | 
| D | Kconfig.kfence | 19 	  Note that, KFENCE is not a substitute for explicit testing with tools76 	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/Documentation/admin-guide/ | 
| D | abi-testing.rst | 1 ABI testing symbols19 .. kernel-abi:: $srctree/Documentation/ABI/testing
 
 | 
| /Linux-v6.6/tools/testing/selftests/arm64/ | 
| D | README | 16       $ make -C tools/testing/selftests TARGETS=arm64 \21       $ make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS="tags signal" \
 
 | 
| /Linux-v6.6/tools/testing/selftests/resctrl/ | 
| D | README | 24  $ make -C tools/testing/selftests TARGETS=resctrl33  $ sudo make -C tools/testing/selftests TARGETS=resctrl run_tests
 44 Build executable file "resctrl_tests" from this directory(tools/testing/selftests/resctrl/):
 
 | 
        12345678910>>...21