Searched full:cases (Results 1 – 25 of 660) sorted by relevance
12345678910>>...27
| /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 …]
|
| D | callbacks.rst | 16 In most cases, (un)patch callbacks will need to be used in conjunction
64 executed. Typical use cases pair a patch handler that acquires and
102 4. Use cases
|
| /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 …]
|
| D | index.rst | 37 of test cases called test suites. The tests either run on kernel boot
39 failed test cases in the kernel log. The test results appear in
87 Arrange-Act-Assert. This is a great way to structure test cases and
|
| /Documentation/admin-guide/ |
| D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
21 Adding the kernel parameter "nomodeset" helps in most cases, but causes
|
| /Documentation/power/regulator/ |
| D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /Documentation/devicetree/bindings/slimbus/ |
| 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
|
| /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
|
| /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
|
| /Documentation/userspace-api/ |
| 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
174 Those cases are:
|
| /Documentation/driver-api/cxl/ |
| 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.
|
| /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 …]
|
| D | 3.Early-stage.rst | 17 clear description of the problem to be solved. In some cases, this step is
63 - Who are the users affected by this problem? Which use cases should the
121 In each of these cases, a great deal of pain and extra work could have been
206 mailing list may not be a viable option. In cases like this, it is worth
210 That said, there are also cases where a company legitimately cannot
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | qcom,bcm-voter.yaml | 34 In most cases, it's necessary to wait in both the AMC and WAKE sets to
36 cases can ensure sufficient delay by other means, then this can be
|
| /Documentation/bpf/ |
| 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
|
| 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 …]
|
| D | prog_flow_dissector.rst | 99 the optional VLAN header and should gracefully handle both cases: when single
101 can be called for both cases and would have to be written carefully to
102 handle both cases.
|
| /Documentation/gpu/rfc/ |
| D | i915_small_bar.rst | 5 I915_MEMORY_CLASS_DEVICE), but in some cases the final BAR size might still be
6 smaller than the total probed_size. In such cases, only some subset of
|
| /Documentation/arch/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 …]
|
| /Documentation/crypto/ |
| D | index.rst | 10 for cryptographic use cases, as well as programming examples.
|
| /Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 65 There are cases in which, even if the general rule given above is followed in
77 In all cases in which kernel code may do something that will confuse AML as a
88 In those cases, however, the above validity considerations must be taken into
|
| /Documentation/i2c/ |
| D | fault-codes.rst | 14 some cases, such as re-initializing (and maybe resetting). After such
34 codes that may be returned, and other cases where these codes should
36 cases (unless the hardware doesn't provide unique fault reports).
|
| /Documentation/ABI/testing/ |
| D | debugfs-cros-ec | 41 the (Intel) processor's SLP_S0 line, in order to detect cases
64 in order to detect cases where a system failed to go into deep
|
| /Documentation/rust/ |
| D | coding-guidelines.rst | 158 reason. In almost all cases, a fallible approach should be used, typically
301 - Conditional compilation triggers the warning in some cases but not others.
303 If there are only a few cases where the warning triggers (or does not
304 trigger) compared to the total number of cases, then one may consider using
309 triggers the warning in some cases but not in others.
339 configuration. Therefore, in cases like this, we cannot use ``expect`` as-is.
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 42 3. Timeouts: In a number of cases such as ChannelPrepare or
61 written in valid registers. In a number of cases the standard even mentions
|
12345678910>>...27