| /kernel/linux/linux-4.19/drivers/gpu/drm/amd/amdgpu/ |
| D | amdgpu_sync.c | 39 bool explicit; member
133 static bool amdgpu_sync_add_later(struct amdgpu_sync *sync, struct dma_fence *f, bool explicit) in amdgpu_sync_add_later() argument
144 e->explicit |= explicit; in amdgpu_sync_add_later()
159 struct dma_fence *f, bool explicit) in amdgpu_sync_fence() argument
169 if (amdgpu_sync_add_later(sync, f, explicit)) in amdgpu_sync_fence()
176 e->explicit = explicit; in amdgpu_sync_fence()
235 /* Ignore fence from the same owner and explicit one as in amdgpu_sync_resv()
298 * @explicit: true if the next fence is explicit
302 struct dma_fence *amdgpu_sync_get_fence(struct amdgpu_sync *sync, bool *explicit) in amdgpu_sync_get_fence() argument
311 if (explicit) in amdgpu_sync_get_fence()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | atomic_ops.rst | 44 proper implicit or explicit read memory barrier is needed before reading the
65 or explicit memory barrier is needed before the value set with the operation
75 implicit or explicit memory barrier is used after possible runtime
79 interface must take care of that with a proper implicit or explicit memory
195 atomic_t value. The first two routines pass explicit integers by
200 require any explicit memory barriers. They need only perform the
213 include explicit memory barriers that are performed before and after
221 If the atomic instructions used in an implementation provide explicit
231 explicit counter adjustment is given instead of the implicit "1".
244 Again, these primitives provide explicit memory barrier semantics around
[all …]
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | atomic_ops.rst | 44 proper implicit or explicit read memory barrier is needed before reading the
65 or explicit memory barrier is needed before the value set with the operation
75 implicit or explicit memory barrier is used after possible runtime
79 interface must take care of that with a proper implicit or explicit memory
195 atomic_t value. The first two routines pass explicit integers by
200 require any explicit memory barriers. They need only perform the
213 include explicit memory barriers that are performed before and after
221 If the atomic instructions used in an implementation provide explicit
231 explicit counter adjustment is given instead of the implicit "1".
244 Again, these primitives provide explicit memory barrier semantics around
[all …]
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | lockdep.txt | 35 Use explicit check expression "c" along with
39 Use explicit check expression "c" along with
43 Use explicit check expression "c" along with
47 Use explicit check expression "c" along with
53 Use explicit check expression "c", and omit all barriers
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | nfp_cppcore.c | 50 * Following fields use explicit locking:
1306 * nfp_cpp_explicit_acquire() - Acquire explicit access handle
1312 * Return: NFP CPP explicit handle
1334 * nfp_cpp_explicit_set_target() - Set target fields for explicit
1335 * @expl: Explicit handle
1353 * nfp_cpp_explicit_set_data() - Set data fields for explicit
1354 * @expl: Explicit handle
1370 * nfp_cpp_explicit_set_signal() - Set signal fields for explicit
1371 * @expl: Explicit handle
1387 * nfp_cpp_explicit_set_posted() - Set completion fields for explicit
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | nfp_cppcore.c | 79 * Following fields use explicit locking:
1299 * nfp_cpp_explicit_acquire() - Acquire explicit access handle
1305 * Return: NFP CPP explicit handle
1327 * nfp_cpp_explicit_set_target() - Set target fields for explicit
1328 * @expl: Explicit handle
1346 * nfp_cpp_explicit_set_data() - Set data fields for explicit
1347 * @expl: Explicit handle
1363 * nfp_cpp_explicit_set_signal() - Set signal fields for explicit
1364 * @expl: Explicit handle
1380 * nfp_cpp_explicit_set_posted() - Set completion fields for explicit
[all …]
|
| /kernel/linux/linux-4.19/crypto/asymmetric_keys/ |
| D | pkcs7.asn1 | 3 content [0] EXPLICIT SignedData OPTIONAL
25 content [0] EXPLICIT Data OPTIONAL
77 aaSequence [2] EXPLICIT SEQUENCE OF AuthenticatedAttribute
78 -- Explicit because easier to compute digest on
|
| /kernel/linux/linux-5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | vxlan_fdb_veto.sh | 73 check_fail $? "FDB with an explicit port not rejected"
78 check_err $? "FDB with an explicit port rejected without extack"
93 check_fail $? "FDB with an explicit port not rejected"
98 check_err $? "FDB with an explicit port rejected without extack"
|
| /kernel/linux/linux-5.10/crypto/asymmetric_keys/ |
| D | pkcs7.asn1 | 3 content [0] EXPLICIT SignedData OPTIONAL
25 content [0] EXPLICIT Data OPTIONAL
77 aaSequence [2] EXPLICIT SEQUENCE OF AuthenticatedAttribute
78 -- Explicit because easier to compute digest on
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | lockdep.rst | 39 Use explicit check expression "c" along with
43 Use explicit check expression "c" along with
47 Use explicit check expression "c" along with
51 Use explicit check expression "c" along with
57 Use explicit check expression "c", and omit all barriers
|
| /kernel/linux/linux-5.10/drivers/target/ |
| D | target_core_alua.c | 33 int *primary, int explicit);
35 struct se_lun *lun, int explicit, int offline);
263 * SET_TARGET_PORT_GROUPS for explicit ALUA operation.
292 * Determine if explicit ALUA via SET_TARGET_PORT_GROUPS is allowed in target_emulate_set_target_port_groups()
748 * Check implicit and explicit ALUA state change request.
751 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
793 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
844 return "Altered by Explicit STPG"; in core_alua_dump_status()
952 * After an explicit target port asymmetric access state in core_alua_queue_state_change_ua()
970 * After an explicit target port asymmetric access in core_alua_queue_state_change_ua()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/block/ |
| D | writeback_cache_control.txt | 2 Explicit volatile write back cache control
20 Explicit cache flushes
28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
|
| /kernel/linux/linux-4.19/drivers/target/ |
| D | target_core_alua.c | 46 int *primary, int explicit);
48 struct se_lun *lun, int explicit, int offline);
276 * SET_TARGET_PORT_GROUPS for explicit ALUA operation.
305 * Determine if explicit ALUA via SET_TARGET_PORT_GROUPS is allowed in target_emulate_set_target_port_groups()
761 * Check implicit and explicit ALUA state change request.
764 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
806 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
857 return "Altered by Explicit STPG"; in core_alua_dump_status()
966 * After an explicit target port asymmetric access state in core_alua_queue_state_change_ua()
984 * After an explicit target port asymmetric access in core_alua_queue_state_change_ua()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | writeback_cache_control.rst | 2 Explicit volatile write back cache control
20 Explicit cache flushes
28 set on an otherwise empty bio structure, which causes only an explicit cache
45 worry if the underlying devices need any explicit cache flushing and how
|
| /kernel/linux/linux-5.10/arch/mips/math-emu/ |
| D | sp_maddf.c | 163 /* Put explicit bit at bit 62 if necessary */ in _sp_maddf()
173 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
181 /* Move explicit bit from bit 23 to bit 62 */ in _sp_maddf()
226 * Put explicit bit at bit 62 if necessary. in _sp_maddf()
235 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
|
| D | dp_maddf.c | 218 /* Put explicit bit at bit 126 if necessary */ in _dp_maddf()
229 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
237 /* Move explicit bit from bit 52 to bit 126 */ in _dp_maddf()
286 * Put explicit bit at bit 126 if necessary. in _dp_maddf()
291 /* MSB of lzm is the explicit bit */ in _dp_maddf()
315 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
|
| /kernel/linux/linux-4.19/arch/mips/math-emu/ |
| D | sp_maddf.c | 174 /* Put explicit bit at bit 62 if necessary */ in _sp_maddf()
184 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
192 /* Move explicit bit from bit 23 to bit 62 */ in _sp_maddf()
237 * Put explicit bit at bit 62 if necessary. in _sp_maddf()
246 * Move explicit bit from bit 62 to bit 26 since the in _sp_maddf()
|
| D | dp_maddf.c | 229 /* Put explicit bit at bit 126 if necessary */ in _dp_maddf()
240 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
248 /* Move explicit bit from bit 52 to bit 126 */ in _dp_maddf()
297 * Put explicit bit at bit 126 if necessary. in _dp_maddf()
302 /* MSB of lzm is the explicit bit */ in _dp_maddf()
326 * Move explicit bit from bit 126 to bit 55 since the in _dp_maddf()
|
| /kernel/linux/linux-4.19/drivers/dma-buf/ |
| D | Kconfig | 4 bool "Explicit Synchronization Framework"
9 The Sync File Framework adds explicit syncronization via
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | preempt-locking.rst | 15 requires explicit additional locking for very few additional situations.
21 RULE #1: Per-CPU data structures need explicit protection
32 First, since the data is per-CPU, it may not have explicit SMP locking, but
132 in doubt, rely on locking or explicit preemption disabling.
|
| /kernel/linux/linux-4.19/arch/ia64/include/asm/sn/ |
| D | tioca_provider.h | 172 * Explicit flushes not needed if GART is in cached mode in tioca_tlbflush()
177 * PV910244: RevA CA needs explicit flushes. in tioca_tlbflush()
179 * flushing otherwise the explicit flush is ignored. in tioca_tlbflush()
196 * Gart in uncached mode ... need an explicit flush. in tioca_tlbflush()
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | preempt-locking.txt | 16 requires explicit additional locking for very few additional situations.
22 RULE #1: Per-CPU data structures need explicit protection
33 First, since the data is per-CPU, it may not have explicit SMP locking, but
133 in doubt, rely on locking or explicit preemption disabling.
|
| /kernel/linux/linux-4.19/include/net/netfilter/ |
| D | nf_tproxy.h | 53 * an explicit iptables rule. In this case the sockets are assumed
63 * regardless if it was bound to 0.0.0.0 or an explicit
64 * address. The reasoning is that if there's an explicit rule, it
|
| /kernel/linux/linux-5.10/include/net/netfilter/ |
| D | nf_tproxy.h | 53 * an explicit iptables rule. In this case the sockets are assumed
63 * regardless if it was bound to 0.0.0.0 or an explicit
64 * address. The reasoning is that if there's an explicit rule, it
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
72 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|