| /linux/Documentation/livepatch/ |
| 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
176 unwinder must report these cases as unreliable.
[all …]
|
| /linux/scripts/coccinelle/misc/ |
| 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
|
| A 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/tools/testing/selftests/tc-testing/ |
| A 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.
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
158 -i, --id Generate ID numbers for new test cases
[all …]
|
| /linux/net/bluetooth/ |
| A 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/Documentation/RCU/ |
| 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/tools/testing/selftests/rcutorture/doc/ |
| A 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/Documentation/devicetree/bindings/slimbus/ |
| A 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/Documentation/dev-tools/kunit/ |
| A D | usage.rst | 499 struct sha1_test_case cases[] = {
509 for (i = 0; i < ARRAY_SIZE(cases); ++i) {
510 sha1sum(cases[i].str, out);
511 KUNIT_EXPECT_STREQ_MSG(test, out, cases[i].sha1,
512 "sha1sum(%s)", cases[i].str);
521 * reduce duplication if test cases can be shared across multiple tests.
524 field and reuse ``cases``.
544 struct sha1_test_case cases[] = {
560 // Creates `sha1_gen_params()` to iterate over `cases`.
561 KUNIT_ARRAY_PARAM(sha1, cases, case_to_desc);
[all …]
|
| /linux/Documentation/gpu/ |
| A 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/Documentation/devicetree/bindings/iommu/ |
| 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/power/regulator/ |
| A D | design.rst | 24 Consumer use cases
36 The consumer API should be structured so that these use cases are
|
| /linux/Documentation/bpf/ |
| A D | bpf_devel_QA.rst | 79 from the current review queue. Likewise for cases where patches would
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
346 Also always make sure to add BPF test cases (e.g. test_bpf.c and
606 Q: In some cases clang flag ``-target bpf`` is used but in other cases the
[all …]
|
| A 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.
|
| 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/tools/testing/selftests/tc-testing/creating-testcases/ |
| A 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/Documentation/powerpc/ |
| 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/tools/testing/selftests/tc-testing/creating-plugins/ |
| A 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/sound/hda/ |
| A 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/arch/m68k/fpsp040/ |
| A D | sto_res.S | 35 cmpib #3,%d0 |check for fp0/fp1 cases
68 cmpib #3,%d0 |check for fp0/fp1 cases
|
| /linux/Documentation/devicetree/bindings/interconnect/ |
| A 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/Documentation/devicetree/bindings/i2c/ |
| A D | i2c-s3c2410.txt | 18 Required for all cases except "samsung,s3c2440-hdmiphy-i2c":
22 cases except for "samsung,s3c2440-hdmiphy-i2c" whose input/output
|
| /linux/Documentation/process/ |
| A D | deprecated.rst | 63 cases is to refactor the code as suggested below to avoid the open-coded
115 is strscpy(), though care must be given to any cases where the return
128 strscpy(), though care must be given to any cases where the return value
131 errno when it truncates). Any cases still needing NUL-padding should
145 though care must be given to any cases where the return value of strlcpy()
185 The C language allows switch cases to fall through to the next case
205 cases, we have adopted a pseudo-keyword macro "fallthrough" which
225 for these cases. The older style of one-element or zero-length arrays should
|
| /linux/tools/testing/selftests/ftrace/ |
| A D | README | 5 shell scripts for testing. Feel free to add new test cases.
38 * The test cases should run on dash (busybox shell) for testing on
|
| /linux/drivers/media/dvb-core/ |
| A D | Kconfig | 65 Should not be enabled on normal cases, as logs can
77 Should not be enabled on normal cases, as logs can
|