| /linux/scripts/kconfig/tests/err_recursive_dep/ |
| A D | expected_stderr | 1 Kconfig:11:error: recursive dependency detected!
4 subsection "Kconfig recursive dependency limitations"
6 Kconfig:5:error: recursive dependency detected!
9 subsection "Kconfig recursive dependency limitations"
11 Kconfig:17:error: recursive dependency detected!
15 subsection "Kconfig recursive dependency limitations"
17 Kconfig:32:error: recursive dependency detected!
21 subsection "Kconfig recursive dependency limitations"
23 Kconfig:37:error: recursive dependency detected!
29 Kconfig:60:error: recursive dependency detected!
[all …]
|
| /linux/drivers/gpu/drm/scheduler/ |
| A D | sched_entity.c | 136 if (READ_ONCE(entity->dependency)) in drm_sched_entity_is_ready()
212 if (job->sched->ops->dependency) in drm_sched_job_dependency()
286 if (entity->dependency) { in drm_sched_entity_fini()
289 dma_fence_put(entity->dependency); in drm_sched_entity_fini()
290 entity->dependency = NULL; in drm_sched_entity_fini()
322 entity->dependency = NULL; in drm_sched_entity_clear_dep()
374 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
386 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
387 entity->dependency = fence; in drm_sched_entity_add_dependency_cb()
401 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
[all …]
|
| /linux/Documentation/kbuild/ |
| A D | Kconfig.recursion-issue-01 | 8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
34 # the "recursive dependency detected" error.
39 # since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
42 # easy to understand. Note that matching semantics on the dependency on
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| A D | kconfig-language.rst | 119 This defines a dependency for this menu entry. If multiple
157 from a direct dependency or with a visible prompt.
198 FOO should imply not only BAZ, but also its dependency BAR::
296 the menu entry, e.g. this means the dependency "NET" is added to the
297 dependency list of the config option NETDEVICES.
302 be part of the dependency list and then one of these two conditions
375 dependency, but will not appear under menuconfig M anymore, because
550 the dependency is not met.
576 Kconfig recursive dependency limitations
580 into a recursive dependency issue with Kconfig, a recursive dependency can be
[all …]
|
| A D | Kconfig.select-break | 1 # Select broken dependency issue
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| /linux/include/trace/events/ |
| A D | timer.h | 400 TP_PROTO(int success, int dependency),
402 TP_ARGS(success, dependency),
406 __field( int , dependency )
411 __entry->dependency = dependency;
415 show_tick_dep_name(__entry->dependency))
|
| /linux/Documentation/locking/ |
| A D | lockdep-design.rst | 22 dependency can be understood as lock order, where L1 -> L2 suggests that
25 dependency just means the order ever happened. The validator maintains a
137 Multi-lock dependency rules:
151 validator will find such dependency circle in arbitrary complexity,
173 dependency rules are enforced:
512 Dependency types and strong dependency paths:
519 For each lock dependency::
565 , we have both X -(SN)-> Y and X -(EN)-> Y in the dependency graph.
571 "strong" path, which indicates the strong dependency throughout each dependency
577 -(SR)-> dependency.
[all …]
|
| /linux/tools/memory-model/Documentation/ |
| A D | control-dependencies.txt | 12 Therefore, a load-load control dependency will not preserve ordering
46 the control dependency.
103 Without explicit memory ordering, control-dependency-based ordering is
161 "if" statement, destroying the control dependency's ordering properties.
172 destroying the control dependency's ordering:
210 ordered CPU would have no dependency of any sort between the load from
232 destroy the control dependency while respecting the letter of the
243 dependency into nonexistence. Careful use of READ_ONCE() or
244 atomic{,64}_read() can help to preserve your control dependency.
247 of the "if" statement containing the control dependency, including
|
| A D | glossary.txt | 9 dependency" extends from that load extending to the later access.
20 address dependency extends from that rcu_dereference() to that
56 a "control dependency" extends from that load to that store.
62 Here, the control dependency extends from the READ_ONCE() on
89 on the value returned by an earlier load, a "data dependency"
95 In this case, the data dependency extends from the READ_ONCE()
100 especially true in cases where the dependency is carried through
|
| A D | cheatsheet.txt | 31 DR: Dependent read (address dependency)
32 DW: Dependent write (address, data, or control dependency)
|
| A D | recipes.txt | 274 against later accesses that depend on the value loaded. A dependency
276 (address dependency, as shown above), the value written by a later store
277 (data dependency), or whether or not a later store is executed in the
278 first place (control dependency). Note that the term "data dependency"
361 control dependency paired with a full memory barrier:
378 This pairing of a control dependency in CPU0() with a full memory
384 control dependency on the kernel side and a full memory barrier on
398 The kernel's control dependency between the load from ->data_tail
555 the LB litmus test, a control dependency was enough to do the
|
| /linux/Documentation/core-api/ |
| A D | refcount-vs-atomic.rst | 64 A control dependency (on success) for refcounters guarantees that
68 Control dependency on stores are not implemented using any explicit
123 * fully ordered --> control dependency on success for stores
152 * fully ordered --> RELEASE ordering + control dependency
167 * fully ordered --> RELEASE ordering + control dependency + hold
|
| /linux/tools/memory-model/litmus-tests/ |
| A D | LB+fencembonceonce+ctrlonceonce.litmus | 9 * combination of a control dependency and a full memory barrier are enough
11 * another control dependency and order would still be maintained.)
|
| /linux/scripts/ |
| A D | dev-needs.sh | 14 /sys/devices and then lists the probe dependency chain (suppliers and
15 parents) of these devices. It does a breadth first search of the dependency
17 dependency chain.
|
| /linux/Documentation/ |
| A D | memory-barriers.txt | 398 (2) Data dependency barriers.
418 dependency barrier.
561 data-dependency barriers.
601 <data dependency barrier>
675 <data dependency barrier> /* BUG: No data dependency!!! */
680 dependency, but rather a control dependency that the CPU may short-circuit
826 defeating control dependency:
909 control dependency.
930 with a data dependency barrier, a control dependency, an acquire barrier,
932 read barrier, control dependency, or a data dependency barrier pairs
[all …]
|
| /linux/Documentation/driver-api/ |
| A D | device_link.rst | 21 Often these two dependency types come together, so a device depends on
27 In its standard or *managed* form, a device link combines *both* dependency
60 represents a driver presence dependency, yet is added from the consumer's
82 driver presence dependency is needed (but only correct suspend/resume and
109 Driver authors should be aware that a driver presence dependency for managed
178 (supplier). A driver presence dependency is not necessary for this
194 * In some SoCs a functional dependency exists from display, video codec and
208 ordering or a driver presence dependency.
235 To prevent introduction of dependency loops into the graph, it is
246 such a device link only makes sense if a driver presence dependency is
|
| /linux/Documentation/driver-api/memory-devices/ |
| A D | ti-gpmc.rst | 28 dependency for certain gpmc timings on gpmc clock frequency. Hence a
54 gpmc timing dependency on peripheral timings:
175 indirect dependency of peripheral timings to gpmc timings other than
|
| /linux/include/drm/ |
| A D | gpu_scheduler.h | 152 struct dma_fence *dependency; member
338 struct dma_fence *(*dependency)(struct drm_sched_job *sched_job, member
|
| /linux/Documentation/networking/ |
| A D | tcp-thin.rst | 15 dependency on the arrival of new data from the application to trigger
22 lifespan. The combination of time-dependency and the fact that the
|
| /linux/drivers/clk/zynqmp/ |
| A D | Kconfig | 9 It has a dependency on the PMU firmware.
|
| /linux/Documentation/crypto/ |
| A D | async-tx-api.rst | 53 2. cross channel dependency chains: the API allows a chain of dependent
99 before the dependency is submitted. This requires that all descriptors be
105 2. submitting an unacknowledged descriptor as a dependency to another
128 it polls for the completion of the operation. It handles dependency
|
| /linux/kernel/bpf/preload/ |
| A D | Kconfig | 10 # The dependency on !COMPILE_TEST prevents it from being enabled
|
| /linux/tools/build/ |
| A D | Build.include | 59 # Copy dependency data into .cmd file
60 # - gcc -M dependency info
|
| /linux/drivers/gpu/drm/i915/ |
| A D | Kconfig.debug | 7 # We use the dependency on !COMPILE_TEST to not be enabled in
146 bool "Enable additional driver debugging for detecting dependency cycles"
208 and also analyze the request dependency resolving timeline.
|
| /linux/drivers/mtd/lpddr/ |
| A D | Kconfig | 23 # ARM dependency is only for writel_relaxed()
|