| /linux/scripts/kconfig/tests/err_recursive_dep/ |
| H A D | expected_stderr | 1 error: recursive dependency detected!
4 subsection "Kconfig recursive dependency limitations"
6 error: recursive dependency detected!
9 subsection "Kconfig recursive dependency limitations"
11 error: recursive dependency detected!
15 subsection "Kconfig recursive dependency limitations"
17 error: recursive dependency detected!
21 subsection "Kconfig recursive dependency limitations"
23 error: recursive dependency detected!
27 subsection "Kconfig recursive dependency limitations"
[all …]
|
| /linux/drivers/gpu/drm/scheduler/ |
| H A D | sched_entity.c | 333 if (entity->dependency) { in drm_sched_entity_fini()
334 dma_fence_remove_callback(entity->dependency, &entity->cb); in drm_sched_entity_fini()
335 dma_fence_put(entity->dependency); in drm_sched_entity_fini()
336 entity->dependency = NULL; in drm_sched_entity_fini()
368 entity->dependency = NULL; in drm_sched_entity_wakeup()
398 struct dma_fence *fence = entity->dependency; in drm_sched_entity_add_dependency_cb()
408 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
421 dma_fence_put(entity->dependency); in drm_sched_entity_add_dependency_cb()
422 entity->dependency = fence; in drm_sched_entity_add_dependency_cb()
426 !test_bit(DMA_FENCE_FLAG_SIGNALED_BIT, &entity->dependency->flags)) in drm_sched_entity_add_dependency_cb()
[all …]
|
| /linux/Documentation/kbuild/ |
| H 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"
|
| H 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/ |
| H A D | timer.h | 428 TP_PROTO(int success, int dependency),
430 TP_ARGS(success, dependency),
434 __field( int , dependency )
439 __entry->dependency = dependency;
443 show_tick_dep_name(__entry->dependency))
|
| /linux/Documentation/locking/ |
| H 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:
375 likely to be linked into the lock-dependency graph. This turns out to
512 Dependency types and strong dependency paths:
519 For each lock dependency::
531 With the above combination for simplification, there are 4 types of dependency edges
535 exclusive writer to recursive reader dependency, "X -(ER)-> Y" means
[all …]
|
| /linux/tools/memory-model/Documentation/ |
| H 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
|
| H 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
|
| H A D | cheatsheet.txt | 31 DR: Dependent read (address dependency)
32 DW: Dependent write (address, data, or control dependency)
|
| H A D | recipes.txt | 278 against later accesses that depend on the value loaded. A dependency
280 (address dependency, as shown above), the value written by a later store
281 (data dependency), or whether or not a later store is executed in the
282 first place (control dependency). Note that the term "data dependency"
365 control dependency paired with a full memory barrier:
382 This pairing of a control dependency in CPU0() with a full memory
388 control dependency on the kernel side and a full memory barrier on
402 The kernel's control dependency between the load from ->data_tail
559 the LB litmus test, a control dependency was enough to do the
|
| /linux/tools/memory-model/litmus-tests/ |
| H 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.)
|
| H A D | dep+plain.litmus | 10 * conditional of P0()'s if-statement creates a control dependency
|
| /linux/scripts/ |
| H 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/ |
| H A D | memory-barriers.txt | 55 - Address-dependency barriers (historical).
189 There is an obvious address dependency here, as the value loaded into D depends
394 address-dependency barriers; see the "SMP barrier pairing" subsection.
397 (2) Address-dependency barriers (historical).
404 An address-dependency barrier is a weaker form of read barrier. In the
407 the second load will be directed), an address-dependency barrier would
411 An address-dependency barrier is a partial ordering on interdependent
417 considered can then perceive. An address-dependency barrier issued by
422 the address-dependency barrier.
427 [!] Note that the first load really has to have an _address_ dependency and
[all …]
|
| /linux/Documentation/driver-api/ |
| H 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/ |
| H 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/Documentation/networking/ |
| H 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/ |
| H A D | Kconfig | 9 It has a dependency on the PMU firmware.
|
| /linux/kernel/bpf/preload/ |
| H A D | Kconfig | 6 # The dependency on !COMPILE_TEST prevents it from being enabled
|
| /linux/Documentation/crypto/ |
| H 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/drivers/mtd/lpddr/ |
| H A D | Kconfig | 23 # ARM dependency is only for writel_relaxed()
|
| /linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_build.rst | 31 dependency installed in /build/root/ and install them together with libbpf
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 7 # We use the dependency on !COMPILE_TEST to not be enabled in
167 bool "Enable additional driver debugging for detecting dependency cycles"
230 and also analyze the request dependency resolving timeline.
|
| /linux/tools/testing/ktest/ |
| H A D | config-bisect.pl | 229 my %dependency;
277 my $arr = $dependency{$config};
|
| /linux/arch/arm64/boot/dts/allwinner/ |
| H A D | sun50i-h64-remix-mini-pc.dts | 181 * dependency between pinctrl, the regulator and the RSB Bus.
257 /* Specifying R_PIO consumer would create circular dependency. */
|