| /kernel/linux/linux-6.6/Documentation/livepatch/ |
| 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 …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/ |
| D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| D | tdc.py | 68 Get all required plugins from the list of test cases and return
86 Get all required plugins from the list of test cases and load any plugin
431 Open the JSON file containing the test cases and return them
468 'selection', 'select which test cases: ' +
471 'action', 'select action to perform on selected test cases')
486 help='Execute the specified test cases with specified IDs')
489 help='List all test cases, or those only within the specified category')
492 help='Display the selected test cases')
495 help='Generate ID numbers for new test cases')
504 help='Execute test cases that use a physical device, ' +
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/tc-testing/ |
| D | README | 59 cases. To disable execution within the namespace, pass the -N option
77 future). A test suite has one or more test cases in it.
106 executed as part of the test. More will be added as test cases require.
111 The NAMES values are used to substitute into the commands in the test cases.
131 Execute test cases that use a physical device, where
137 select which test cases: files plus directories; filtered by categories
150 Execute the specified test cases with specified IDs
153 select action to perform on selected test cases
155 -l, --list List all test cases, or those only within the
157 -s, --show Display the selected test cases
[all …]
|
| /kernel/linux/linux-5.10/net/bluetooth/ |
| D | Kconfig | 119 cases are run first thing at module load time. When the Bluetooth
120 subsystem is compiled into the kernel image, then the test cases
124 bool "ECDH test cases"
127 Run test cases for ECDH cryptographic functionality used by the
131 bool "SMP test cases"
134 Run test cases for SMP cryptographic functionality, including both
|
| /kernel/linux/linux-6.6/net/bluetooth/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/dev-tools/kunit/ |
| 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 …]
|
| /kernel/linux/linux-5.10/scripts/coccinelle/misc/ |
| 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
|
| /kernel/linux/linux-6.6/scripts/coccinelle/misc/ |
| 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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/creating-testcases/ |
| 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
81 in the test cases. tdc will output a series of TAP results for the skipped
|
| /kernel/linux/linux-6.6/tools/testing/selftests/tc-testing/creating-testcases/ |
| 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
|
| /kernel/linux/linux-6.6/tools/usb/ |
| 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:'
|
| /kernel/linux/linux-5.10/tools/usb/ |
| 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:'
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | bpf_devel_QA.rst | 79 from the current review queue. Likewise for cases where patches would
198 at the end of the week. In some cases pull requests could additionally
217 Q: Verifier changes and test cases
219 Q: I made a BPF verifier change, do I need to add test cases for
223 it is absolutely necessary to add test cases to the BPF kernel
228 cases, including a lot of corner cases that LLVM BPF back end may
229 generate out of the restricted C code. Thus, adding test cases is
231 affect prior use-cases. Thus, treat those test cases as: verifier
244 The more test cases we add to BPF selftests, the better the coverage
311 commit is in net-next (or in some cases bpf-next). The ``Fixes:`` tag is
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iommu/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/slimbus/ |
| D | bus.txt | 18 In some cases it may be necessary to describe non-probeable device
20 such cases, child nodes for those devices will be present as
28 Instance ID Is for the cases where multiple Devices of the
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| 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 …]
|
| /kernel/linux/linux-6.6/arch/mips/math-emu/ |
| 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()
|
| /kernel/linux/linux-5.10/arch/mips/math-emu/ |
| 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()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | device-io.rst | 78 writes have occurred in the specific cases the author cares. This kind
80 cases, the read used to flush the device may be expected to fail (if the
109 complete. In many cases, however, the driver may want to indicate that the
112 these cases, although only some platforms will honor the relaxed
115 provides examples of how to use readX_relaxed(). In many cases, a majority
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| 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 …]
|