| /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 …]
|
| H A D | __init__.py | 3 Detect recursive dependency error.
5 Recursive dependency should be treated as an error.
|
| /linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 7 Address Dependency: When the address of a later memory access is computed
9 dependency" extends from that load extending to the later access.
20 address dependency extends from that rcu_dereference() to that
25 See also "Control Dependency" and "Data Dependency".
54 Control Dependency: When a later store's execution depends on a test
56 a "control dependency" extends from that load to that store.
62 Here, the control dependency extends from the READ_ONCE() on
67 See also "Address Dependency" and "Data Dependency"
[all...] |
| 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 | 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/Documentation/kbuild/ |
| H A D | kconfig-language.rst | 123 This defines a dependency for this menu entry. If multiple
167 from a direct dependency or with a visible prompt.
198 FOO should imply not only BAZ, but also its dependency BAR::
273 module state. Dependency expressions have the following syntax::
332 the menu entry, e.g. this means the dependency "NET" is added to the
333 dependency list of the config option NETDEVICES.
338 be part of the dependency list and then one of these two conditions
411 dependency, but will not appear under menuconfig M anymore, because
468 This defines an if block. The dependency expression <expr> is appended
539 to describe the dependency on the compiler feature is to use "depends on"
[all …]
|
| 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"
|
| /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/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()
359 * drm_sched_entity_wakeup - callback to clear the entity's dependency and
368 entity->dependency = NULL; in drm_sched_entity_wakeup()
391 * Add a callback to the current dependency of the entity to wake up the
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()
[all …]
|
| /linux/tools/testing/selftests/ |
| H A D | kselftest_deps.sh | 24 echo " failed the build dependency check from the TARGETS in Selftests"
26 echo "- Prints pass/fail dependency check for each tests/sub-test."
28 echo "- Default: runs dependency checks on all tests."
128 # that need dependency checks. Find them and append them to the tests
141 # Use the default value and filter out pkg-config for dependency check.
267 echo "FAIL: $test dependency check: $lib" >> $fail
274 echo "PASS: $test dependency check passed $lib" >> $pass
287 echo -e "Kselftest Dependency Check for [$0 $1 $2] results..."
305 echo -e "Targets passed build dependency check on system:"
313 echo -e "Targets failed build dependency check on system:"
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | i915_deps.c | 121 * i915_deps_sync - Wait for all the fences in the dependency collection
126 * This function waits for fences in the dependency collection. If it
155 * i915_deps_add_dependency - Add a fence to the dependency collection
161 * Adds a fence to the dependency collection, and takes a reference on it.
164 * dependency collection. If the fence context is not zero and there was
171 * error. If an error was returned, the dependency collection will be
211 * i915_deps_add_resv - Add the fences of a reservation object to a dependency
|
| /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/kernel/locking/ |
| H A D | lockdep.c | 416 * We put the lock dependency chains into a hash-table as well, to cache
442 * The hash key of the lock dependency chains is a hash itself too:
1422 * Add a new dependency to the head of the list:
1431 * Lock not present yet - get a new dependency struct and in add_lock_to_list()
1464 * indicates that adding the <prev> -> <next> lock dependency will
1562 * Return the forward or backward dependency list.
1564 * @lock: the lock_list to get its class's dependency list
1608 * For dependency @prev -> @next:
1707 * Breadth-First Search to find a strong path in the dependency graph.
1717 * e.g. ER and SN) between two nodes in the dependency graph. But
[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/arch/arm/mach-omap2/ |
| H A D | clockdomain.c | 130 * "autodep" is a clockdomain sleep/wakeup dependency that is
181 * _clkdm_add_wkdep - add a wakeup dependency from clkdm2 to clkdm1 (lockless)
230 * Remove a wakeup dependency causing @clkdm1 to wake up when @clkdm2
269 * _clkdm_add_sleepdep - add a sleep dependency from clkdm2 to clkdm1 (lockless)
277 * dependencies, -ENOENT if the specified dependency cannot be set in
297 pr_debug("clockdomain: hardware cannot set/clear sleep dependency affecting %s from %s\n", in _clkdm_add_sleepdep()
322 * -ENOENT if the specified dependency cannot be cleared in hardware, or
342 pr_debug("clockdomain: hardware cannot set/clear sleep dependency affecting %s from %s\n", in _clkdm_del_sleepdep()
582 * clkdm_add_wkdep - add a wakeup dependency from clkdm2 to clkdm1
613 * clkdm_del_wkdep - remove a wakeup dependency from clkdm2 to clkdm1
[all …]
|
| H A D | clockdomain.h | 147 * @clkdm_add_wkdep: Add a wakeup dependency between clk domains
148 * @clkdm_del_wkdep: Delete a wakeup dependency between clk domains
149 * @clkdm_read_wkdep: Read wakeup dependency state between clk domains
151 * @clkdm_add_sleepdep: Add a sleep dependency between clk domains
152 * @clkdm_del_sleepdep: Delete a sleep dependency between clk domains
153 * @clkdm_read_sleepdep: Read sleep dependency state between clk domains
|
| H A D | pm44xx.c | 38 * struct static_dep_map - Static dependency map
163 * The dynamic dependency between MPUSS -> MEMIF and
187 * omap4plus_init_static_deps() - Initialize a static dependency map
202 pr_err("Failed lookup %s or %s for wakeup dependency\n", in omap4plus_init_static_deps()
208 pr_err("Failed to add %s -> %s wakeup dependency(%d)\n", in omap4plus_init_static_deps()
|
| /linux/scripts/basic/ |
| H A D | fixdep.c | 27 * the dependency on autoconf.h by a dependency on every config
67 * and will read the dependency file <depfile>
69 * The transformed dependency snipped is written to stdout.
76 * process filtering out the dependency on autoconf.h and adding
174 /* Print out a dependency path from a symbol name. */ in use_config()
314 * assume the first dependency after a colon as the in parse_dep_file()
359 * Do not list the source file as dependency, so that kbuild is in parse_dep_file()
372 * rustc emits the same dependency list for each in parse_dep_file()
|
| /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;
442 TP_printk("success=%d dependency=%s", __entry->success, \
443 show_tick_dep_name(__entry->dependency))
|
| /linux/crypto/async_tx/ |
| H A D | async_tx.c | 39 * @submit: transaction dependency and submission modifiers
59 * async_tx_channel_switch - queue an interrupt descriptor with a dependency
80 /* attached dependency, flush the parent channel */ in async_tx_channel_switch()
133 * to prevent a circular locking dependency with drivers that already
154 /* sanity check the dependency chain: in async_tx_submit()
|
| /linux/include/linux/ |
| H A D | lockdep_types.h | 208 * One-way hash of the dependency chain up to this point. We
209 * hash the hashes step by step as the dependency chain grows.
211 * We use it for dependency-caching and we skip detection
212 * passes and dependency-updates if there is a cache-hit, so
214 * to have a unique key value for every unique dependency path
|
| /linux/tools/build/ |
| H A D | fixdep.c | 67 /* Don't write any target names into the dependency file */ in parse_dep_file()
69 /* The /next/ file is the first dependency */ in parse_dep_file()
78 * Do not list the source file as dependency, in parse_dep_file()
87 * multiple dependency files, only in parse_dep_file()
|
| /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.
37 dependency). If you want to follow these links
291 # We don't need to worry about a cycle in the dependency chain causing
|
| /linux/scripts/kconfig/tests/no_write_if_dep_unmet/ |
| H A D | __init__.py | 3 Do not write choice values to .config if the dependency is unmet.
6 for symbols with unmet dependency.
|
| /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.)
|