Searched refs:dependencies (Results 1 – 25 of 115) sorted by relevance
12345
| /Linux-v6.1/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.
|
| D | Kbuild.include | 23 # The temporary file to save gcc -MMD generated dependencies must not
130 # if_changed_dep - as if_changed, but uses fixdep to reveal dependencies
172 # Execute the command and also postprocess generated .d dependencies file.
|
| /Linux-v6.1/tools/memory-model/Documentation/ |
| D | control-dependencies.txt | 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
211 "a" and the store to "c". In short, control dependencies provide ordering
[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-v6.1/Documentation/kbuild/ |
| 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
|
| 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 …]
|
| /Linux-v6.1/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-v6.1/drivers/gpu/drm/scheduler/ |
| D | sched_main.c | 605 xa_init_flags(&job->dependencies, XA_FLAGS_ALLOC); in drm_sched_job_init()
666 xa_for_each(&job->dependencies, index, entry) { in drm_sched_job_add_dependency()
672 xa_store(&job->dependencies, index, fence, GFP_KERNEL); in drm_sched_job_add_dependency()
679 ret = xa_alloc(&job->dependencies, &id, fence, xa_limit_32b, GFP_KERNEL); in drm_sched_job_add_dependency()
755 xa_for_each(&job->dependencies, index, fence) { in drm_sched_job_cleanup()
758 xa_destroy(&job->dependencies); in drm_sched_job_cleanup()
|
| D | sched_entity.c | 219 if (!xa_empty(&job->dependencies)) in drm_sched_job_dependency()
220 return xa_erase(&job->dependencies, job->last_dependency++); in drm_sched_job_dependency()
|
| /Linux-v6.1/mm/kfence/ |
| D | .kunitconfig | 5 # Additional dependencies.
|
| /Linux-v6.1/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-v6.1/Documentation/driver-api/ |
| D | dma-buf.rst | 225 Common to all these schemes is that userspace controls the dependencies of these
230 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
231 of dependencies injected due to memory management or scheduler decisions.
233 * Only userspace knows about all dependencies in indefinite fences and when
257 through memory management dependencies which userspace is unaware of, which
260 architecture there is no single entity with knowledge of all dependencies.
263 The only solution to avoid dependencies loops is by not allowing indefinite
330 - Only a fairly theoretical option would be to untangle these dependencies when
|
| /Linux-v6.1/tools/testing/selftests/futex/ |
| D | README | 30 o External dependencies shall remain as minimal as possible. Currently gcc
31 and glibc are the only dependencies.
|
| /Linux-v6.1/tools/testing/kunit/configs/ |
| D | all_tests.config | 5 # any tests whose dependencies are already satisfied. Please feel free to add
|
| /Linux-v6.1/Documentation/translations/zh_CN/admin-guide/ |
| D | init.rst | 34 4) **二进制存在但依赖项不可用Binary exists but dependencies not available** ：
|
| /Linux-v6.1/Documentation/translations/zh_TW/admin-guide/ |
| D | init.rst | 37 4) **二進位存在但依賴項不可用Binary exists but dependencies not available** ：
|
| /Linux-v6.1/Documentation/ |
| D | Kconfig | 6 This option makes the Kernel to check for missing dependencies,
|
| /Linux-v6.1/drivers/net/wireless/ti/ |
| D | Kconfig | 18 # keep last for automatic dependencies
|
| /Linux-v6.1/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 …]
|
| /Linux-v6.1/drivers/media/platform/mediatek/vcodec/ |
| D | Kconfig | 16 # our dependencies, to avoid missing symbols during link.
|
| /Linux-v6.1/tools/build/ |
| D | Build.include | 26 # The temporary file to save gcc -MD generated dependencies must not
74 # dependencies in the cmd file
|
| /Linux-v6.1/Documentation/livepatch/ |
| D | cumulative-patches.rst | 5 There might be dependencies between livepatches. If multiple patches need
58 - Decrease user confusion about dependencies between livepatches.
|
| /Linux-v6.1/tools/tracing/rtla/ |
| D | Makefile | 85 echo "** NOTICE: Failed build dependencies"; \
|
| /Linux-v6.1/Documentation/bpf/libbpf/ |
| D | libbpf_build.rst | 6 libelf and zlib are internal dependencies of libbpf and thus are required to link
|
12345
