| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | control-dependencies.txt | 1 CONTROL DEPENDENCIES
4 A major difficulty with control dependencies is that current compilers
7 control dependencies also pose other challenges, which leads to the
11 One such challenge is that control dependencies order only later stores.
32 (usually) guaranteed for load-store control dependencies, as in the
39 Control dependencies can pair with each other and with other types
59 It is tempting to try use control dependencies to enforce ordering on
145 to relying on control dependencies to produce this ordering, you should
182 In addition, control dependencies apply only to the then-clause and
208 The control dependencies would then extend only to the pair of cmov
[all …]
|
| D | README | 29 and cannot do to control dependencies: control-dependencies.txt
53 control-dependencies.txt
55 your control dependencies.
|
| D | glossary.txt | 10 Address dependencies are quite common in RCU read-side critical
22 dependencies. Please see Documentation/RCU/rcu_dereference.rst
63 line 1 to the WRITE_ONCE() on line 2. Control dependencies are
65 Please see control-dependencies.txt for more information.
96 on line 1 to the WRITE_ONCE() on line 2. Data dependencies are
|
| /Linux-v5.15/arch/arm/mach-omap2/ |
| D | clockdomains2xxx_3xxx_data.c | 11 * dependencies for the OMAP2/3 chips. Some notes:
16 * software-controllable dependencies. Non-software-controllable
17 * dependencies do exist, but they are not encoded below (yet).
19 * 24xx does not support programmable sleep dependencies (SLEEPDEP)
27 * XXX encode hardware fixed wakeup dependencies -- esp. for 3430 CORE
32 * -> Port the Sleep/Wakeup dependencies for the domains
49 * Clockdomain dependencies for wkdeps/sleepdeps
51 * XXX Hardware dependencies (e.g., dependencies that cannot be
57 /* 2xxx-specific possible dependencies */
|
| D | clockdomains2430_data.c | 10 * This file contains clockdomains and clockdomain wakeup dependencies
15 * wkdep_srcs are really just software-controllable dependencies.
16 * Non-software-controllable dependencies do exist, but they are not
19 * 24xx does not support programmable sleep dependencies (SLEEPDEP)
27 * XXX encode hardware fixed wakeup dependencies -- esp. for 3430 CORE
32 * -> Port the Sleep/Wakeup dependencies for the domains
47 * Clockdomain dependencies for wkdeps
49 * XXX Hardware dependencies (e.g., dependencies that cannot be
55 /* 2430-specific possible wakeup dependencies */
126 * XXX add usecounting for clkdm dependencies, otherwise the presence
[all …]
|
| D | clockdomains2420_data.c | 10 * This file contains clockdomains and clockdomain wakeup dependencies
15 * wkdep_srcs are really just software-controllable dependencies.
16 * Non-software-controllable dependencies do exist, but they are not
19 * 24xx does not support programmable sleep dependencies (SLEEPDEP)
27 * XXX encode hardware fixed wakeup dependencies -- esp. for 3430 CORE
32 * -> Port the Sleep/Wakeup dependencies for the domains
47 * Clockdomain dependencies for wkdeps
49 * XXX Hardware dependencies (e.g., dependencies that cannot be
55 /* 2420-specific possible wakeup dependencies */
|
| D | clockdomains3xxx_data.c | 11 * dependencies for the OMAP3xxx chips. Some notes:
16 * software-controllable dependencies. Non-software-controllable
17 * dependencies do exist, but they are not encoded below (yet).
25 * XXX encode hardware fixed wakeup dependencies -- esp. for 3430 CORE
30 * -> Port the Sleep/Wakeup dependencies for the domains
45 * Clockdomain dependencies for wkdeps/sleepdeps
47 * XXX Hardware dependencies (e.g., dependencies that cannot be
51 /* OMAP3-specific possible dependencies */
299 * XXX add usecounting for clkdm dependencies, otherwise the presence
312 * XXX add usecounting for clkdm dependencies, otherwise the presence
[all …]
|
| D | clockdomain.c | 158 * @clkdm: clockdomain that we are resolving dependencies for
175 …WARN(!cd->clkdm, "clockdomain: %s: could not find clkdm %s while resolving dependencies - should n… in _resolve_clkdm_deps()
277 * dependencies, -ENOENT if the specified dependency cannot be set in
321 * that does not support software-configurable hardware sleep dependencies,
413 * Register clockdomain "automatic dependencies." These are
414 * clockdomain wakeup and sleep dependencies that are automatically
652 * wakeup dependencies. Wakeup dependencies fixed in hardware are not
681 * clkdm_clear_all_wkdeps - remove all wakeup dependencies from target clkdm
682 * @clkdm: struct clockdomain * to remove all wakeup dependencies from
684 * Remove all inter-clockdomain wakeup dependencies that could cause
[all …]
|
| D | clockdomain.h | 76 * struct clkdm_dep - encode dependencies between clockdomains
79 * @wkdep_usecount: Number of wakeup dependencies causing this clkdm to wake
85 * XXX Should also include hardware (fixed) dependencies.
149 * @clkdm_clear_all_wkdeps: Remove all wakeup dependencies from the clk domain
153 * @clkdm_clear_all_sleepdeps: Remove all sleep dependencies from the clk domain
|
| /Linux-v5.15/scripts/ |
| D | dev-needs.sh | 25 -c lists the compatible string of the dependencies
26 -d lists the driver name of the dependencies that have probed
27 -m lists the module name of the dependencies that have a module
28 -f list the firmware node path of the dependencies
29 -g list the dependencies as edges and nodes for graphviz
30 -t list the dependencies as edges for tsort
32 The filter options provide a way to filter out some dependencies:
33 --allow-no-driver By default dependencies that don't have a driver
41 dependencies.
44 dependencies.
[all …]
|
| D | Kbuild.include | 19 # The temporary file to save gcc -MMD generated dependencies must not
105 # if_changed_dep - as if_changed, but uses fixdep to reveal dependencies
145 # Execute the command and also postprocess generated .d dependencies file.
205 # This is no use for dependencies or $(wildcard). We need to strip the
217 # be prefixed to *both* command invocation and dependencies.
225 # the wrong thing, but we don't really care. The actual dependencies
|
| /Linux-v5.15/Documentation/kbuild/ |
| D | kconfig-language.rst | 24 Every entry has its own dependencies. These dependencies are used
44 the config option, input prompt, dependencies, help text and default
72 to the user. Optionally dependencies only for this prompt can be added
86 Optionally, dependencies only for this default value can be added with
115 Optionally dependencies for this default value can be added with "if".
117 - dependencies: "depends on" <expr>
120 dependencies are defined, they are connected with '&&'. Dependencies
133 - reverse dependencies: "select" <symbol> ["if" <expr>]
135 While normal dependencies reduce the upper limit of a symbol (see
136 below), reverse dependencies can be used to force a lower limit of
[all …]
|
| D | Kconfig.select-break | 17 # visit the dependencies of the select target (in this case B). And since
18 # Kconfig does not visit the dependencies, it breaks the dependencies of B
|
| /Linux-v5.15/arch/arm/mach-nomadik/ |
| D | Makefile | 5 # Note! Dependencies are done automagically by 'make dep', which also
6 # removes any old dependencies. DON'T put your own dependencies here
|
| /Linux-v5.15/arch/xtensa/platforms/xtfpga/ |
| D | Makefile | 4 # Note! Dependencies are done automagically by 'make dep', which also
5 # removes any old dependencies. DON'T put your own dependencies here
|
| /Linux-v5.15/scripts/kconfig/ |
| D | expr.h | 108 * if it is a boolean or tristate. Calculated from prompt dependencies,
109 * which also inherit dependencies from enclosing menus, choices, and
122 /* Dependencies from enclosing menus, choices, and ifs */
125 /* Reverse dependencies through being selected by other symbols */
129 * "Weak" reverse dependencies through being implied by other symbols
241 * 'visible if' dependencies. If more than one is given, they will be
247 * Ordinary dependencies from e.g. 'depends on' and 'if', ANDed
|
| D | menu.c | 296 * and propagate parent dependencies before moving on. in menu_finalize()
332 * Propagate parent dependencies to the child menu in menu_finalize()
360 * 1. The property lacks dependencies in menu_finalize()
375 * Propagate parent dependencies to the in menu_finalize()
389 * dependencies of the selected/implied symbol in menu_finalize()
452 * dependencies contain sym and are a "superset" of in menu_finalize()
453 * sym's dependencies, e.g. '(sym || Q) && R' when sym in menu_finalize()
504 * values' dependencies were propagated to their in menu_finalize()
530 * and only add dependencies. in menu_finalize()
721 * dependencies. For these, we print only the dependencies to improve in get_prompt_str()
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/i915/ |
| D | i915_scheduler.c | 100 * will ensure that dependencies are emitted in fifo. in i915_sched_lookup_priolist()
103 * dependencies that reordering may be visible. in i915_sched_lookup_priolist()
186 * a flat list of all dependencies starting with the current request. in __i915_schedule()
187 * As we walk the list of dependencies, we add all of its dependencies in __i915_schedule()
189 * request) and continue to walk onwards onto the new dependencies. The in __i915_schedule()
203 * (redundant dependencies are not eliminated) and across in __i915_schedule()
425 /* Dependencies along the same timeline are expected. */ in i915_request_show_with_schedule()
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | init.rst | 23 4) **Binary exists but dependencies not available**: E.g. required library
24 dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or
33 library dependencies). And before tackling scripts, better first test a
|
| /Linux-v5.15/tools/testing/selftests/ |
| D | kselftest_deps.sh | 5 # Checks for kselftest build dependencies on the build system.
20 echo "- Parses all test/sub-test Makefile to find library dependencies."
22 echo " in the test Makefiles to identify missing library dependencies."
29 echo "- Optional test name can be specified to check dependencies for it."
242 echo -e "Checked tests defining LDLIBS dependencies"
244 echo -e "Total tests with Dependencies:"
|
| /Linux-v5.15/Documentation/driver-api/ |
| D | dma-buf.rst | 234 Common to all these schemes is that userspace controls the dependencies of these
239 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
240 of dependencies injected due to memory management or scheduler decisions.
242 * Only userspace knows about all dependencies in indefinite fences and when
266 through memory management dependencies which userspace is unaware of, which
269 architecture there is no single entity with knowledge of all dependencies.
272 The only solution to avoid dependencies loops is by not allowing indefinite
339 - Only a fairly theoretical option would be to untangle these dependencies when
|
| /Linux-v5.15/scripts/basic/ |
| D | fixdep.c | 2 * "Optimize" a list of dependencies as spit out by gcc -MD
15 * gcc produces a very nice and correct list of dependencies which
42 * So to get dependencies right, there are two issues:
77 * dependencies on include/config/MY_OPTION for every
83 * correctness, since that can only give too many dependencies, thus
262 /* Ignore certain dependencies */
|
| /Linux-v5.15/arch/x86/kernel/cpu/ |
| D | cpuid-deps.c | 1 /* Declare dependencies between CPUIDs */
15 * This only includes dependencies that can be usefully disabled, not
110 /* Collect all features to disable, handling dependencies */ in do_clear_cpu_cap()
|
| /Linux-v5.15/samples/bpf/ |
| D | README.rst | 7 Build dependencies
34 There are usually dependencies to header files of the current kernel.
70 (build dependencies are ninja, cmake and gcc-c++)::
|
| /Linux-v5.15/Documentation/locking/ |
| D | lockdep-design.rst | 20 the dependencies between different lock-classes. Lock usage indicates
26 continuing effort to prove lock usages and dependencies are correct or
156 Furthermore, the following usage based lock dependencies are not allowed
192 Exception: Nested data dependencies leading to nested locking
302 single-task locking dependencies in the kernel as possible, at least
514 Lock dependencies record the orders of the acquisitions of a pair of locks, and
516 dependencies, but we can show that 4 types of lock dependencies are enough for
551 Note that given two locks, they may have multiple dependencies between them,
572 in the path, as the path that doesn't have two conjunct edges (dependencies) as
574 walking to another through the lock dependencies, and if X -> Y -> Z is in the
[all …]
|
