Searched refs:cases (Results 1 – 25 of 727) sorted by relevance
12345678910>>...30
| /linux-5.19.10/tools/testing/memblock/ |
| D | TODO | 4 1. Add verbose output (e.g., what is being tested and how many tests cases are
17 test cases. Use realloc to adjust the size accordingly.
19 4. Add test cases using this functions (implement them for both directions):
|
| /linux-5.19.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
|
| 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-5.19.10/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-5.19.10/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-5.19.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 …]
|
| /linux-5.19.10/tools/testing/selftests/bpf/prog_tests/ |
| D | libbpf_probes.c | 98 } cases[] = { in test_libbpf_probe_helpers() local
109 size_t case_cnt = ARRAY_SIZE(cases), i; in test_libbpf_probe_helpers()
113 const struct case_def *d = &cases[i]; in test_libbpf_probe_helpers()
|
| /linux-5.19.10/Documentation/dev-tools/kunit/ |
| D | usage.rst | 66 additional tests cases which would test each property that an ``add`` function
124 We need many test cases covering all the unit's behaviors. It is common to have
127 *test suite*. A test suite is a collection of test cases for a unit of code
151 ``example_suite_init``, then run the test cases ``example_test_foo``,
179 not depend on physical hardware. Some of our test cases may not need hardware,
212 however, it is an easily derived concept. Accordingly, in most cases, every
449 In complicated cases, we recommend using a *table-driven test* compared to the
462 struct sha1_test_case cases[] = {
472 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
473 sha1sum(cases[i].str, out);
[all …]
|
| D | index.rst | 30 of test cases called test suites. The tests either run on kernel boot
32 failed test cases in the kernel log. The test results appear in `TAP
79 Arrange-Act-Assert. This is a great way to structure test cases and
|
| /linux-5.19.10/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-5.19.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
|
| /linux-5.19.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
|
| /linux-5.19.10/Documentation/power/regulator/ |
| D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /linux-5.19.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
|
| /linux-5.19.10/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::
155 module. Use/Test-cases:
178 - Add support for cloned writeback outputs and related test cases using a
|
| /linux-5.19.10/sound/hda/ |
| D | Kconfig | 41 # A fallback is provided so that the code compiles in all cases.
48 # A fallback is provided so that the code compiles in all cases.
|
| /linux-5.19.10/tools/testing/selftests/tc-testing/creating-testcases/ |
| 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
81 in the test cases. tdc will output a series of TAP results for the skipped
|
| /linux-5.19.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 …]
|
| /linux-5.19.10/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-5.19.10/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
|
| /linux-5.19.10/arch/m68k/fpsp040/ |
| D | sto_res.S | 35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
|
| /linux-5.19.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 …]
|
| /linux-5.19.10/scripts/atomic/fallbacks/ |
| D | dec_and_test | 8 * cases.
|
| D | inc_and_test | 8 * other cases.
|
| /linux-5.19.10/Documentation/devicetree/bindings/usb/ |
| D | brcm,bcm3384-usb.txt | 7 systems, special handling may be needed in the following cases:
|
12345678910>>...30