| /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, ))
|
| /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/tools/testing/selftests/bpf/prog_tests/ |
| H A D | prog_tests_framework.c | 69 } cases[] = { in test_prog_tests_framework_expected_msgs() local
164 for (i = 0; i < ARRAY_SIZE(cases); i++) { in test_prog_tests_framework_expected_msgs()
165 if (test__start_subtest(cases[i].name)) { in test_prog_tests_framework_expected_msgs()
167 msgs.patterns = cases[i].pats; in test_prog_tests_framework_expected_msgs()
169 for (j = 0; cases[i].pats[j].substr; j++) in test_prog_tests_framework_expected_msgs()
171 validate_msgs(cases[i].log, &msgs, dummy_emit); in test_prog_tests_framework_expected_msgs()
174 if (cases[i].expected) in test_prog_tests_framework_expected_msgs()
175 ASSERT_HAS_SUBSTR(env.subtest_state->log_buf, cases[i].expected, "expected output"); in test_prog_tests_framework_expected_msgs()
|
| /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/net/lib/py/ |
| H A D | ksft.py | 236 ksft_run(cases=[my_case], args=(cfg, ))
238 Will generate cases:
281 def _ksft_generate_test_cases(cases, globs, case_pfx, args): argument
284 cases = cases or []
294 cases.append(value)
297 for func in cases:
315 def ksft_run(cases=None, globs=None, case_pfx=None, args=()): argument
316 test_cases = _ksft_generate_test_cases(cases, globs, case_pfx, args)
|
| /linux/Documentation/driver-api/acpi/ |
| H A D | acpi-drivers.rst | 14 at least in some cases, there are problems with it, related to general
19 hardware and in many cases they provide auxiliary information on devices
51 value, and device IDs are not used in those cases. In consequence, confusingly
64 For consistency, this approach has been extended to the cases in which ACPI
65 device IDs are used. Namely, in those cases, an additional device object is
69 hardware actually is. There are even cases in which multiple devices are
|
| /linux/Documentation/virt/kvm/ |
| H A D | review-checklist.rst | 42 All features contributed to KVM, and in many cases bugfixes too, should be
78 supporting them in QEMU and/or ``kvmtool``. In some cases selftests
80 test corner cases in guest state save/restore.
93 In some cases the affected code is run for any guests and functional
102 Selftests should test corner cases of the APIs, and should also cover
110 test at least API error cases. Guest operation can be covered by
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | usage.rst | 6 Test Cases
66 additional tests cases which would test each property that an ``add`` function
164 We need many test cases covering all the unit's behaviors. It is common to have
167 *test suite*. A test suite is a collection of test cases for a unit of code
196 ``example_suite_init``, then run the test cases ``example_test_foo``,
229 not depend on physical hardware. Some of our test cases may not need hardware,
262 however, it is an easily derived concept. Accordingly, in most cases, every
499 In complicated cases, we recommend using a *table-driven test* compared to the
512 struct sha1_test_case cases[] = {
522 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
[all …]
|
| /linux/tools/usb/ |
| H A D | hcd-tests.sh | 37 # NOTE: the 'in' and 'out' cases are usually bulk, but can be
106 echo '** Control test cases:'
124 echo '** Host Write (OUT) test cases:'
155 echo '** Host ISOCHRONOUS Write (OUT) test cases:'
182 echo '** Host Read (IN) test cases:'
208 echo '** Host ISOCHRONOUS Read (IN) test 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
|
| /linux/tools/testing/selftests/tc-testing/creating-testcases/ |
| H A D | AddingTestCases.txt | 1 tdc - Adding test cases for tdc
5 ADDING TEST CASES
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/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 …]
|
| H A D | ringbuf.rst | 42 Additionally, given the performance of BPF ringbuf, many use cases would just
64 a replacement for perf buffer use cases), to a complicated application
103 pointer directly to ring buffer memory. In a lot of cases records are larger
109 due to extra memory copy, covers some use cases that are not suitable for
114 code. Discard is useful for some advanced use-cases, such as ensuring
203 buffer. For extreme cases, when BPF program wants more manual control of
|
| /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/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/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/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/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/arch/mips/math-emu/ |
| H A D | sp_maddf.c | 46 * Handle the cases when at least one of x, y or z is a NaN. in _sp_maddf()
64 /* ZERO z cases are handled separately below */ in _sp_maddf()
84 * Cases of addition of infinities with opposite signs in _sp_maddf()
105 /* Handle cases +0 + (-0) and similar ones. */ in _sp_maddf()
108 * Cases of addition of zeros of equal signs in _sp_maddf()
|
| /linux/Documentation/driver-api/cxl/ |
| H A D | maturity-map.rst | 10 continues to respond to new use cases with new features, capability
29 - [2] Stabilizing: Major functionality operational, common cases are
30 mature, but known corner cases are still a work in progress.
49 in place, but there are several corner cases that are pending closure.
92 mainly caused by the enumeration corner cases above.
|
| /linux/arch/arm/probes/kprobes/ |
| H A D | test-core.h | 8 #define VERBOSE 0 /* Set to '1' for more logging of test cases */
32 * The arguments given to test cases can be one of three types.
85 * Building blocks for test cases.
95 * Some specific test cases may make use of other custom constructs.
198 * Macros to define test cases.
200 * Those of the form TEST_{R,P,M}* can be used to define test cases
439 /* Various values used in test cases... */
|
| /linux/tools/testing/selftests/tc-testing/ |
| H 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
|
| /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/Documentation/devicetree/bindings/slimbus/ |
| H A D | slimbus.yaml | 39 In some cases it may be necessary to describe non-probeable device
40 details such as non-standard ways of powering up a device. In such cases,
54 - Instance ID, can be used for the cases where multiple devices of
|