| /linux/tools/testing/selftests/drivers/net/hw/ |
| H 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, ))
|
| H A D | tso.py | 241 cases = []
249 cases += [
254 cases.append(test_builder(info[0], cfg, outer_ipver, info[2], None, outer_ipver))
256 ksft_run(cases=cases, args=(cfg, ))
|
| H A D | devlink_rate_tc_bw.py | 418 Main entry point for running the test cases.
432 cases = [test_no_tc_mapping_bandwidth, test_tc_mapping_bandwidth]
434 ksft_run(cases=cases, args=(cfg,))
|
| /linux/tools/testing/selftests/net/lib/py/ |
| H A D | ksft.py | 218 ksft_run(cases=[my_case], args=(cfg, ))
220 Will generate cases:
263 def _ksft_generate_test_cases(cases, globs, case_pfx, args):
266 cases = cases or []
276 cases.append(value)
279 for func in cases:
297 def ksft_run(cases=None, globs=None, case_pfx=None, args=()):
298 test_cases = _ksft_generate_test_cases(cases, globs, case_pfx, args)
213 ksft_run(cases=None, globs=None, case_pfx=None, args=()) global() argument
|
| /linux/tools/testing/selftests/net/ |
| H 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:
|
| /linux/scripts/coccinelle/misc/ |
| H A D | cond_no_effect.cocci | 5 // There can be false positives in cases where the positional
7 // is a placeholder for not yet handled cases.
17 // the two known cases are:
38 // All other cases look like bugs or at least lack of documentation
|
| H A D | badty.cocci | 4 //# This makes an effort to find cases where the argument to sizeof is wrong
7 //# to the the memory being allocated. There are false positives in cases the
|
| /linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 41 In some cases it is legitimate to omit specific functions from the trace,
42 but all other functions must be reported. These cases are described in
45 Secondly, the reliable stacktrace function must be robust to cases where
47 function should attempt to detect such cases and return a non-zero error
49 an unsafe way. Specific cases are described in further detail below.
55 To ensure that kernel code can be correctly unwound in all cases,
63 In some cases, an unwinder may require metadata to correctly unwind.
115 To ensure that such cases do not result in functions being omitted from a
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
[all …]
|
| /linux/net/bluetooth/ |
| H A D | Kconfig | 130 cases are run first thing at module load time. When the Bluetooth
131 subsystem is compiled into the kernel image, then the test cases
135 bool "ECDH test cases"
138 Run test cases for ECDH cryptographic functionality used by the
142 bool "SMP test cases"
145 Run test cases for SMP cryptographic functionality, including both
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H 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()
|
| /linux/tools/testing/selftests/rcutorture/doc/ |
| H 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.
|
| /linux/Documentation/RCU/ |
| H A D | rcuref.rst | 11 those unusual cases where percpu-ref would consume too much memory,
82 update (write) stream. In such cases, atomic_inc_not_zero() might be
84 use atomic_inc() in such cases.
87 search_and_reference() code path. In such cases, the
139 In cases where delete() can sleep, synchronize_rcu() can be called from
|
| /linux/Documentation/power/regulator/ |
| H A D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /linux/sound/hda/core/ |
| H A D | Kconfig | 26 # A fallback is provided so that the code compiles in all cases.
34 # A fallback is provided so that the code compiles in all cases.
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | iommu.txt | 44 the specific IOMMU. Below are a few examples of typical use-cases:
51 In such cases the number of cells will usually be 1 as in the next case.
53 in order to enable translation for a given master. In such cases the single
54 address cell corresponds to the master device's ID. In some cases more than
62 Note that these are merely examples and real-world use-cases may use different
85 have a means to turn off translation. But it is invalid in such cases to
|
| /linux/Documentation/process/ |
| H A D | deprecated.rst | 63 cases is to refactor the code as suggested below to avoid the open-coded
129 is strscpy(), though care must be given to any cases where the return
144 strscpy(), though care must be given to any cases where the return value
147 errno when it truncates). Any cases still needing NUL-padding should
153 attribute to avoid future compiler warnings. For cases still needing
162 though care must be given to any cases where the return value of strlcpy()
202 The C language allows switch cases to fall through to the next case
222 cases, we have adopted a pseudo-keyword macro "fallthrough" which
242 for these cases. The older style of one-element or zero-length arrays should
350 There are two special cases of replacement where the DECLARE_FLEX_ARRAY()
[all …]
|
| /linux/Documentation/userspace-api/ |
| H A D | mseal.rst | 57 - For above error cases, users can expect the given memory range is
59 - There might be other internal errors/cases not listed here, e.g.
61 number of supported VMAs. In those cases, partial updates to the given
62 memory range could happen. However, those cases should be rare.
125 Use cases
195 Those cases are:
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H 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
|
| /linux/lib/kunit/ |
| H A D | Kconfig | 81 In most cases this should be left as Y. Only if additional opt-in
93 In most cases this should be left as Y. Only if additional opt-in
124 Sets the default timeout, in seconds, for Kunit test cases. This value
131 cases.
|
| /linux/tools/testing/selftests/tc-testing/creating-plugins/ |
| H 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.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | index.rst | 28 of test cases called test suites. The tests either run on kernel boot
30 failed test cases in the kernel log. The test results appear in
78 Arrange-Act-Assert. This is a great way to structure test cases and
|
| /linux/Documentation/arch/powerpc/ |
| H A D | ultravisor.rst | 312 Use cases
386 Use cases
437 Use cases
483 Use cases
544 Use cases
593 Use cases
638 Use cases
673 Use cases
720 Use cases
770 Use cases
[all …]
|
| /linux/arch/m68k/fpsp040/ |
| H A D | sto_res.S | 35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
|
| /linux/tools/net/sunrpc/xdrgen/generators/ |
| H A D | union.py | 68 for case in node.cases:
156 for case in node.cases:
240 for case in node.cases:
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 106 from the current review queue. Likewise for cases where patches would
228 at the end of the week. In some cases pull requests could additionally
248 Q: Verifier changes and test cases
250 Q: I made a BPF verifier change, do I need to add test cases for
254 it is absolutely necessary to add test cases to the BPF kernel
259 cases, including a lot of corner cases that LLVM BPF back end may
260 generate out of the restricted C code. Thus, adding test cases is
262 affect prior use-cases. Thus, treat those test cases as: verifier
275 The more test cases we add to BPF selftests, the better the coverage
342 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|