| /linux/scripts/ |
| A 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.
|
| /linux/tools/testing/selftests/kvm/x86_64/ |
| A D | xcr0_cpuid_test.c | 22 #define ASSERT_XFEATURE_DEPENDENCIES(supported_xcr0, xfeatures, dependencies) \ argument
24 uint64_t __supported = (supported_xcr0) & ((xfeatures) | (dependencies)); \
27 __supported == ((xfeatures) | (dependencies)), \
29 __supported, (xfeatures), (dependencies)); \
|
| /linux/tools/memory-model/Documentation/ |
| A 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
219 (*) Control dependencies can order prior loads against later stores.
[all …]
|
| A D | README | 34 and cannot do to control dependencies: control-dependencies.txt
68 control-dependencies.txt
70 your control dependencies.
|
| A 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/Documentation/kbuild/ |
| A 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
|
| A D | kconfig-language.rst | 24 Every entry has its own dependencies. These dependencies are used
121 - dependencies: "depends on" <expr>
137 - reverse dependencies: "select" <symbol> ["if" <expr>]
149 a symbol to a value without visiting the dependencies.
163 - weak reverse dependencies: "imply" <symbol> ["if" <expr>]
245 Menu dependencies
427 possible options are dependencies.
509 config option to 'y' no matter the dependencies.
552 Architecture and platform dependencies
576 Optional dependencies
[all …]
|
| /linux/Documentation/admin-guide/ |
| A 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/mm/kfence/ |
| A D | .kunitconfig | 5 # Additional dependencies.
|
| /linux/Documentation/driver-api/ |
| A D | pwrseq.rst | 30 define dependencies in the form of other units that must be enabled before
36 dependencies) that a consumer selects by its name when requesting a handle
66 (units) and define their dependencies. They can then expose named targets that
|
| A D | dma-buf.rst | 259 Common to all these schemes is that userspace controls the dependencies of these
264 * Only the kernel knows about all DMA fence dependencies, userspace is not aware
265 of dependencies injected due to memory management or scheduler decisions.
267 * Only userspace knows about all dependencies in indefinite fences and when
291 through memory management dependencies which userspace is unaware of, which
294 architecture there is no single entity with knowledge of all dependencies.
297 The only solution to avoid dependencies loops is by not allowing indefinite
364 - Only a fairly theoretical option would be to untangle these dependencies when
|
| /linux/samples/bpf/ |
| A D | README.rst | 13 Build dependencies
44 There are usually dependencies to header files of the current kernel.
80 (build dependencies are ninja, cmake and gcc-c++)::
|
| /linux/drivers/gpu/drm/ci/xfails/ |
| A D | requirements.txt | 4 # ci-collate dependencies
|
| /linux/drivers/gpu/drm/xe/ |
| A D | .kunitconfig | 1 # xe dependencies
|
| /linux/drivers/gpu/drm/scheduler/ |
| A D | sched_entity.c | 208 xa_for_each(&job->dependencies, index, f) { in drm_sched_entity_kill_jobs_cb()
226 xa_erase(&job->dependencies, index); in drm_sched_entity_kill_jobs_cb()
464 f = xa_load(&job->dependencies, job->last_dependency); in drm_sched_job_dependency()
|
| A D | sched_main.c | 814 xa_init_flags(&job->dependencies, XA_FLAGS_ALLOC); in drm_sched_job_init()
875 xa_for_each(&job->dependencies, index, entry) { in drm_sched_job_add_dependency()
881 xa_store(&job->dependencies, index, fence, GFP_KERNEL); in drm_sched_job_add_dependency()
888 ret = xa_alloc(&job->dependencies, &id, fence, xa_limit_32b, GFP_KERNEL); in drm_sched_job_add_dependency()
1011 xa_for_each(&job->dependencies, index, fence) { in drm_sched_job_cleanup()
1014 xa_destroy(&job->dependencies); in drm_sched_job_cleanup()
|
| /linux/tools/testing/selftests/futex/ |
| A D | README | 30 o External dependencies shall remain as minimal as possible. Currently gcc
31 and glibc are the only dependencies.
|
| /linux/tools/memory-model/litmus-tests/ |
| A D | dep+plain.litmus | 7 * carry dependencies much like accesses to registers:
|
| /linux/Documentation/translations/zh_CN/admin-guide/ |
| A D | init.rst | 34 4) **二进制存在但依赖项不可用Binary exists but dependencies not available** ：
|
| /linux/drivers/net/wireless/ti/ |
| A D | Kconfig | 18 # keep last for automatic dependencies
|
| /linux/Documentation/devicetree/bindings/crypto/ |
| A D | ti,omap-sham.yaml | 36 dependencies:
|
| /linux/Documentation/locking/ |
| A 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
32 class and hence their usages and dependencies will contribute to those of
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,
574 walking to another through the lock dependencies, and if X -> Y -> Z is in the
[all …]
|
| /linux/Documentation/devicetree/bindings/nvmem/ |
| A D | nvmem-consumer.yaml | 33 dependencies:
|
| /linux/Documentation/translations/zh_TW/admin-guide/ |
| A D | init.rst | 37 4) **二進制存在但依賴項不可用Binary exists but dependencies not available** ：
|
| /linux/Documentation/devicetree/bindings/net/nfc/ |
| A D | nxp,pn532.yaml | 33 dependencies:
|