| /Linux-v5.15/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 …]
|
| /Linux-v5.15/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 …]
|
| /Linux-v5.15/net/bluetooth/ |
| D | Kconfig | 126 cases are run first thing at module load time. When the Bluetooth
127 subsystem is compiled into the kernel image, then the test cases
131 bool "ECDH test cases"
134 Run test cases for ECDH cryptographic functionality used by the
138 bool "SMP test cases"
141 Run test cases for SMP cryptographic functionality, including both
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | usage.rst | 50 Test Cases
110 create additional tests cases which would each test a different property that an
178 many test cases covering all of a unit's behaviors. Consequently it is common
181 concept of a *test suite*. A *test suite* is just a collection of test cases
206 cases ``example_test_foo``, ``example_test_bar``, and ``example_test_baz``;
465 In such cases, it can be helpful to have a helper macro or function, e.g. this
487 In some cases, it can be helpful to write a *table-driven test* instead, e.g.
499 struct sha1_test_case cases[] = {
509 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
510 sha1sum(cases[i].str, out);
[all …]
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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:'
|
| /Linux-v5.15/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 …]
|
| 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-v5.15/Documentation/gpu/ |
| D | vkms.rst | 103 - kms_plane: some test cases are failing due to timeout on capturing CRC;
105 - kms_flip: when running test cases in sequence, some successful individual
106 test cases are failing randomly; when individually, some successful test
107 cases display in the log the following error::
157 module. Use/Test-cases:
180 - Add support for cloned writeback outputs and related test cases using a
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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
|
| /Linux-v5.15/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()
|
| /Linux-v5.15/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 …]
|
| /Linux-v5.15/tools/testing/selftests/rcutorture/doc/ |
| 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-v5.15/arch/arm/probes/kprobes/ |
| 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-v5.15/include/dt-bindings/mux/ |
| D | mux.h | 5 * Most Multiplexer bindings specify an idle state. In most cases, the
6 * multiplexer can be left as is when idle, and in some cases it can
|
| /Linux-v5.15/tools/testing/selftests/tc-testing/creating-plugins/ |
| 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-v5.15/lib/ |
| D | test_linear_ranges.c | 23 * which generate test cases to test the existing functions - and by default
37 * ...chances are you also need to fix the test cases. In sunny day you fix one
43 * can implement few, carefully selected simple UT-cases which test this. I've
46 * expected. I am not covering all the cases but I will see the logic should be
51 * working. And I definitely don't want to add 500+ test cases that break when
|
| /Linux-v5.15/tools/testing/selftests/bpf/ |
| D | bpf_rlimit.h | 12 /* For the sake of running the test cases, we temporarily in bpf_rlimit_ctor()
14 * errors from actual test cases and not getting noise in bpf_rlimit_ctor()
|
| /Linux-v5.15/lib/kunit/ |
| D | kunit-example-test.c | 73 * Here we make a list of all the test cases we want to add to the test suite
80 * use KUnit, just know that this is how you associate test cases with a
92 * Test cases are defined as belonging to the suite by adding them to
|
| /Linux-v5.15/drivers/gpio/ |
| D | TODO | 73 gpiolib-of.c: in some cases subsystems are doing custom flags and
99 In some cases it makes sense to create a GPIO chip from the local driver
110 cases, and the helper library should be as helpful as possible for MMIO
129 The GPIOLIB irqchip is a helper irqchip for "simple cases" that should
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| 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
|
