| /tools/testing/selftests/drivers/net/hw/ |
| A D | csum.py | 94 cases = []
96 cases.append(test_builder("rx_tcp", cfg, ipver, False, "-t"))
97 cases.append(test_builder("rx_tcp_invalid", cfg, ipver, False, "-t -E"))
99 cases.append(test_builder("rx_udp", cfg, ipver, False, ""))
100 cases.append(test_builder("rx_udp_invalid", cfg, ipver, False, "-E"))
102 cases.append(test_builder("tx_udp_csum_offload", cfg, ipver, True, "-U"))
103 cases.append(test_builder("tx_udp_zero_checksum", cfg, ipver, True, "-U -Z"))
105 ksft_run(cases=cases, args=(cfg, ))
|
| A D | tso.py | 240 cases = []
248 cases += [
253 … cases.append(test_builder(info[0], cfg, outer_ipver, info[2], None, outer_ipver))
255 ksft_run(cases=cases, args=(cfg, ))
|
| A D | devlink_rate_tc_bw.py | 458 cases = [test_no_tc_mapping_bandwidth, test_tc_mapping_bandwidth]
460 ksft_run(cases=cases, args=(cfg,))
|
| /tools/testing/selftests/net/lib/py/ |
| A D | ksft.py | 213 def ksft_run(cases=None, globs=None, case_pfx=None, args=()): argument
214 cases = cases or []
222 cases.append(value)
232 print("1.." + str(len(cases)), flush=True)
237 for case in cases:
|
| /tools/testing/selftests/rcutorture/doc/ |
| A D | TINY_RCU.txt | 1 This document gives a brief rationale for the TINY_RCU test cases.
19 In common code tested by TREE_RCU test cases.
|
| A D | initrd.txt | 3 very long sleep() call. In both cases, this creation is done by
|
| A D | TREE_RCU-kconfig.txt | 2 cases, a group that includes PREEMPT_RCU.
|
| /tools/testing/selftests/net/ |
| A D | link_netns.py | 67 cases = [
75 for src_net, netns, link_netns, exp1, exp2 in cases:
106 cases = [
118 for src_net, netns, link_netns, peer_netns, exp in cases:
|
| /tools/testing/selftests/bpf/prog_tests/ |
| A D | libbpf_probes.c | 102 } cases[] = { in test_libbpf_probe_helpers() local
113 size_t case_cnt = ARRAY_SIZE(cases), i; in test_libbpf_probe_helpers()
117 const struct case_def *d = &cases[i]; in test_libbpf_probe_helpers()
|
| /tools/testing/selftests/tc-testing/creating-plugins/ |
| A D | AddingPlugins.txt | 15 - adding commands to be run before and/or after the test cases
16 - adding commands to be run before and/or after the execute phase of the test cases
59 the TAP output for the extra test cases.
|
| /tools/net/sunrpc/xdrgen/generators/ |
| A D | union.py | 61 for case in node.cases:
143 for case in node.cases:
224 for case in node.cases:
|
| /tools/testing/selftests/tc-testing/creating-testcases/ |
| A D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
10 template.json for the required JSON format for test cases.
18 If you wish to store your custom test cases elsewhere, be sure to run
83 in the test cases. tdc will output a series of TAP results for the skipped
|
| /tools/testing/selftests/ftrace/ |
| A 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/net/sunrpc/xdrgen/ |
| A D | xdr_ast.py | 450 cases: List[_XdrCaseSpec]
456 for case in self.cases:
467 for case in self.cases:
694 cases = body.children[1:-1]
697 return _XdrUnion(name, discriminant, cases, default)
|
| /tools/testing/selftests/tc-testing/ |
| A D | README | 58 cases. To disable execution within the namespace, pass the -N option
76 future). A test suite has one or more test cases in it.
114 executed as part of the test. More will be added as test cases require.
119 The NAMES values are used to substitute into the commands in the test cases.
205 Jamal Hadi Salim, for providing valuable test cases
|
| /tools/testing/selftests/arm64/signal/ |
| A D | README | 24 - Signals' test-cases hereafter defined belong currently to two
56 In both cases test results are expected in terms of:
|
| /tools/memory-model/litmus-tests/ |
| A D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 13 * full barrier for each non-rf link. (Exceptions include some cases
|
| /tools/memory-model/Documentation/ |
| A D | glossary.txt | 21 "p->a". In rare cases, optimizing compilers can destroy address
70 name suggests. And in a great many cases, a pair of CPUs is all
71 that is required. In other cases, the notion of pairing must be
100 especially true in cases where the dependency is carried through
|
| A D | simple.txt | 121 by the percpu_counter infrastructure. In many cases, there are already
146 For more sophisticated use cases, LKMM can guide you, including use
147 cases involving combining sequence locking with other synchronization
223 WRITE_ONCE() can safely be used in some cases. These primitives provide
265 More complex use cases
|
| /tools/testing/ktest/examples/ |
| A D | README | 7 and commented to show more generic use cases that are more helpful for
|
| /tools/thermal/tmon/ |
| A D | README | 18 thermal conditions are often exception cases that hard to reach in
|
| /tools/testing/selftests/kselftest_harness/ |
| A D | harness-selftest.expected | 3 # Starting 9 tests from 4 test cases.
|
| /tools/scripts/ |
| A D | utilities.mak | 187 # errors for one of the cases flex generates code C compilers complains about.
197 # one of the cases flex generates code C compilers complains about.
|
| /tools/testing/selftests/futex/ |
| A D | README | 8 odd corner cases, regression tests, and abject abuse and misuse.
|
| /tools/perf/Documentation/ |
| A D | cpu-and-latency-overheads.txt | 17 These overheads may be significantly different in some cases. For example,
|