Searched refs:testing (Results 1 – 25 of 25) sorted by relevance
| /tools/testing/selftests/rcutorture/ |
| D | Makefile | 3 ( cd ../../../..; tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs TREE01 )
|
| /tools/testing/selftests/rcutorture/bin/ |
| D | kvm-recheck-rcuperf.sh | 20 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
|
| D | kvm-recheck.sh | 16 PATH=`pwd`/tools/testing/selftests/rcutorture/bin:$PATH; export PATH
|
| D | mkinitrd.sh | 10 D=tools/testing/selftests/rcutorture
|
| D | kvm.sh | 191 if test -z "$TORTURE_INITRD" || tools/testing/selftests/rcutorture/bin/mkinitrd.sh
|
| /tools/ |
| D | Makefile | 84 $(call descend,testing/$@)
117 $(call descend,testing/$(@:_install=),install)
164 $(call descend,testing/$(@:_clean=),clean)
|
| /tools/testing/selftests/rcutorture/doc/ |
| D | initrd.txt | 5 by tools/testing/selftests/rcutorture/bin/mkinitrd.sh.
12 cd tools/testing/selftests/rcutorture
|
| D | TINY_RCU.txt | 10 The theory here is that randconfig testing will hit the other six possible
|
| D | TREE_RCU-kconfig.txt | 67 Always used in KVM testing.
|
| /tools/testing/ktest/examples/ |
| D | README | 10 crosstests.conf - this config shows an example of testing a git repo against
17 used to perform real testing.
|
| /tools/perf/Documentation/ |
| D | build-xed.txt | 13 Basic xed testing:
|
| D | db-export.txt | 30 backward compatibility by testing for the presence of new tables and columns
|
| /tools/testing/selftests/powerpc/alignment/ |
| D | alignment_handler.c | 54 int testing; variable
61 if (!testing) { in sighandler()
139 testing = 1; in test_memcpy()
143 testing = 0; in test_memcpy()
|
| /tools/testing/selftests/ftrace/ |
| D | README | 5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on
|
| /tools/testing/selftests/zram/ |
| D | README | 29 Commands required for testing:
|
| /tools/testing/selftests/livepatch/ |
| D | README | 31 % make -C tools/testing/selftests TARGETS=livepatch run_tests
|
| /tools/io_uring/ |
| D | README | 24 and contains a number of unit tests as well for testing io_uring. It also
|
| /tools/testing/selftests/media_tests/ |
| D | regression_test.txt | 15 cd tools/testing/selftests/media_tests
|
| /tools/testing/selftests/net/forwarding/ |
| D | README | 29 This approach for testing switch ASICs has several advantages over the
|
| /tools/testing/selftests/tc-testing/ |
| D | README | 1 tdc - Linux Traffic Control (tc) unit testing suite
185 bjb@bee:~/work/tc-testing$ ls -l plugins
234 while also setting up dummy devices to be used in testing.
254 first version of the tc testing suite. This work was presented at
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| D | AddingTestCases.txt | 42 under test is testing. Example: filter, actions, u32, gact, etc.
44 succeeds. For example: if testing a filter, the command to create
|
| /tools/perf/tests/attr/ |
| D | README | 3 This testing support is embedded into perf directly and is governed
|
| /tools/power/cpupower/bench/ |
| D | README-BENCH | 13 - Possibly Real time priority testing? -> what happens if there are
|
| /tools/testing/selftests/android/ion/ |
| D | README | 59 linux$ make -C tools/testing/selftests TARGETS=android run_tests
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-prog.rst | 151 Run BPF program *PROG* in the kernel testing infrastructure
|