| /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-5.10/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | nfp_cppcore.c | 50 * Following fields use explicit locking:
1308 * nfp_cpp_explicit_acquire() - Acquire explicit access handle
1314 * Return: NFP CPP explicit handle
1336 * nfp_cpp_explicit_set_target() - Set target fields for explicit
1337 * @expl: Explicit handle
1355 * nfp_cpp_explicit_set_data() - Set data fields for explicit
1356 * @expl: Explicit handle
1372 * nfp_cpp_explicit_set_signal() - Set signal fields for explicit
1373 * @expl: Explicit handle
1389 * nfp_cpp_explicit_set_posted() - Set completion fields for explicit
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | nfp_cppcore.c | 50 * Following fields use explicit locking:
1307 * nfp_cpp_explicit_acquire() - Acquire explicit access handle
1313 * Return: NFP CPP explicit handle
1335 * nfp_cpp_explicit_set_target() - Set target fields for explicit
1336 * @expl: Explicit handle
1354 * nfp_cpp_explicit_set_data() - Set data fields for explicit
1355 * @expl: Explicit handle
1371 * nfp_cpp_explicit_set_signal() - Set signal fields for explicit
1372 * @expl: Explicit handle
1388 * nfp_cpp_explicit_set_posted() - Set completion fields for explicit
[all …]
|
| /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-6.6/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-6.6/Documentation/RCU/ |
| D | lockdep.rst | 41 Use explicit check expression "c" along with
45 Use explicit check expression "c" along with
49 Use explicit check expression "c" along with
53 Use explicit check expression "c" along with
61 Use explicit check expression "c", and omit all barriers
|
| /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-6.6/tools/testing/selftests/drivers/net/mlxsw/ |
| D | vxlan_fdb_veto.sh | 88 check_fail $? "FDB with an explicit port not rejected"
93 check_err $? "FDB with an explicit port rejected without extack"
108 check_fail $? "FDB with an explicit port not rejected"
113 check_err $? "FDB with an explicit port rejected without extack"
|
| /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-6.6/drivers/target/ |
| D | target_core_alua.c | 33 int *primary, int explicit);
35 struct se_lun *lun, int explicit, int offline);
266 * SET_TARGET_PORT_GROUPS for explicit ALUA operation.
295 * Determine if explicit ALUA via SET_TARGET_PORT_GROUPS is allowed in target_emulate_set_target_port_groups()
725 * Check implicit and explicit ALUA state change request.
728 core_alua_check_transition(int state, int valid, int *primary, int explicit) in core_alua_check_transition() argument
770 if (!(valid & ALUA_T_SUP) || explicit) in core_alua_check_transition()
821 return "Altered by Explicit STPG"; in core_alua_dump_status()
927 * After an explicit target port asymmetric access state in core_alua_queue_state_change_ua()
944 * After an explicit target port asymmetric access in core_alua_queue_state_change_ua()
[all …]
|
| /kernel/linux/linux-6.6/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/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-6.6/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-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-6.6/arch/loongarch/ |
| D | Makefile | 52 # When the assembler supports explicit relocation hint, we must use it.
56 # When the assembler does not supports explicit relocation hint, we can't use
65 # Also, -mdirect-extern-access is useful in case of building with explicit
74 cflags-y += $(call cc-option,-mno-explicit-relocs)
|
| /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-6.6/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-5.10/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.
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | cgroup_subsys.h | 5 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
76 * DO NOT ADD ANY SUBSYSTEM WITHOUT EXPLICIT ACKS FROM CGROUP MAINTAINERS.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | tdm-slot.txt | 18 to specify an explicit mapping of the channels and the slots. If it's absent
26 The explicit masks are given as array of integers, where the first
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | tdm-slot.txt | 18 to specify an explicit mapping of the channels and the slots. If it's absent
26 The explicit masks are given as array of integers, where the first
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/ |
| D | drm_gem_atomic_helper.c | 148 * explicit fencing interfaces on the atomic ioctl. in drm_gem_plane_helper_prepare_fb()
150 * This way explicit fencing can be used to overrule implicit fencing, in drm_gem_plane_helper_prepare_fb()
151 * which is important to make explicit fencing use-cases work: One in drm_gem_plane_helper_prepare_fb()
154 * the slower screen, whereas explicit fence allows 2 independent in drm_gem_plane_helper_prepare_fb()
156 * obeys both implicit and explicit fences for plane updates, then it in drm_gem_plane_helper_prepare_fb()
157 * will break all the benefits of explicit fencing. in drm_gem_plane_helper_prepare_fb()
|