Home
last modified time | relevance | path

Searched refs:testing (Results 1 – 25 of 338) sorted by relevance

12345678910>>...14

/Linux-v5.4/Documentation/dev-tools/
Dkselftest.rst5 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 default location, which is tools/testing/selftests/kselftest, or in a
134 $ cd tools/testing/selftests
[all …]
/Linux-v5.4/Documentation/driver-api/rapidio/
Dsysfs.rst6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
/Linux-v5.4/tools/
DMakefile84 $(call descend,testing/$@)
117 $(call descend,testing/$(@:_install=),install)
164 $(call descend,testing/$(@:_clean=),clean)
/Linux-v5.4/Documentation/fault-injection/
Dnotifier-error-inject.rst91 There are tools/testing/selftests using the notifier error injection features
94 * tools/testing/selftests/cpu-hotplug/on-off-test.sh
95 * tools/testing/selftests/memory-hotplug/on-off-test.sh
Dfault-injection.rst199 This feature is intended for systematic testing of faults in a single
361 tools/testing/fault-injection/failcmd.sh. Please run a command
362 "./tools/testing/fault-injection/failcmd.sh --help" for more information and
367 Run a command "make -C tools/testing/selftests/ run_tests" with injecting slab
370 # ./tools/testing/fault-injection/failcmd.sh \
371 -- make -C tools/testing/selftests/ run_tests
376 # ./tools/testing/fault-injection/failcmd.sh --times=100 \
377 -- make -C tools/testing/selftests/ run_tests
383 ./tools/testing/fault-injection/failcmd.sh --times=100 \
384 -- make -C tools/testing/selftests/ run_tests
/Linux-v5.4/Documentation/gpu/
Dvkms.rst70 - Writeback connector. This is useful for testing compositors if you don't have
79 We already have vgem, which is a gem driver for testing rendering, similar to
80 how vkms is for testing the modeset side. Adding buffer sharing support to vkms
91 testing. Also needs support to specify the EDID.
/Linux-v5.4/tools/testing/selftests/rcutorture/doc/
Dinitrd.txt5 by tools/testing/selftests/rcutorture/bin/mkinitrd.sh.
12 cd tools/testing/selftests/rcutorture
/Linux-v5.4/tools/testing/ktest/examples/
DREADME10 crosstests.conf - this config shows an example of testing a git repo against
17 used to perform real testing.
/Linux-v5.4/drivers/scsi/aacraid/
DTODO2 o More testing
/Linux-v5.4/tools/testing/selftests/rcutorture/
DMakefile3 ( cd ../../../..; tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs TREE01 )
/Linux-v5.4/tools/testing/selftests/powerpc/alignment/
Dalignment_handler.c54 int testing; variable
61 if (!testing) { in sighandler()
139 testing = 1; in test_memcpy()
143 testing = 0; in test_memcpy()
/Linux-v5.4/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck-rcuperf.sh20 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
/Linux-v5.4/drivers/acpi/apei/
DKconfig60 mainly used for debugging and testing the other parts of
69 if you want to debugging and testing the ERST kernel support
/Linux-v5.4/drivers/net/wireless/ath/
DKconfig50 bool "Atheros dynamic user regulatory testing"
55 undergoing certification testing.
/Linux-v5.4/drivers/net/wireless/
DKconfig77 tristate "Simulated radio testing tool for mac80211"
80 This driver is a developer testing tool that can be used to test
82 needed for normal wireless LAN usage and is only for testing. See
/Linux-v5.4/drivers/net/ieee802154/
DKconfig122 tristate "Simulated radio testing tool for mac802154"
124 This driver is a developer testing tool that can be used to test
126 needed for normal wpan usage and is only for testing.
/Linux-v5.4/Documentation/usb/
Dindex.rst19 gadget-testing
/Linux-v5.4/Documentation/networking/
Deql.txt11 1.1.86. Some testing with 1.1.92 has been done with the v1.1 patch
29 my testing so far, the Livingston PortMaster 2e's load-balancing is a
225 I have not yet done any load-balancing testing for PPP devices, mainly
246 All testing I have done was with two 28.8 V.FC modems, one connecting
339 Although you may already done this performance testing, here
354 I have done some testing of this software, with two goals in
383 about 160 kbits/sec. The next round of testing will distribute
/Linux-v5.4/drivers/base/test/
DKconfig7 testing asynchronous driver probing by the device core.
/Linux-v5.4/drivers/soc/fsl/qbman/
DKconfig42 high-level API testing with them (whichever portal(s) are affine
56 high-level API testing with them (whichever portal(s) are affine to
/Linux-v5.4/Documentation/isdn/
Dcredits.rst48 For testing and help to get into kernel.
69 For heavy-duty-beta-testing with his BBS ;)
/Linux-v5.4/samples/bpf/
DMakefile60 CGROUP_HELPERS := ../../tools/testing/selftests/bpf/cgroup_helpers.o
61 TRACE_HELPERS := ../../tools/testing/selftests/bpf/trace_helpers.o
176 KBUILD_HOSTCFLAGS += -I$(srctree)/tools/testing/selftests/bpf/
286 -I$(srctree)/tools/testing/selftests/bpf/ \
/Linux-v5.4/Documentation/ABI/
DREADME20 testing/
53 the "testing" stage, so that kernel developers can work
69 Interfaces in the testing state can move to the stable state when the
/Linux-v5.4/Documentation/power/
Dindex.rst13 drivers-testing
/Linux-v5.4/tools/testing/selftests/ftrace/
DREADME5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on

12345678910>>...14