| /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 …]
|
| D | nfp6000_pcie.c | 109 /* The number of explicit BARs to reserve.
162 /* Explicit IO access */
164 struct mutex mutex; /* Lock access to this explicit group */
352 /* We don't match explicit bars through the area interface */ in matching_bar()
532 * BAR0.4: Reserved for Explicit 0.0-0.3 access
533 * BAR0.5: Reserved for Explicit 1.0-1.3 access
534 * BAR0.6: Reserved for Explicit 2.0-2.3 access
535 * BAR0.7: Reserved for Explicit 3.0-3.3 access
684 "0.%d: Explicit%d, ", 4 + i, i); in enable_bars()
950 /* Unaligned? Translate to an explicit access */ in nfp6000_area_read()
[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-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/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-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-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-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-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-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-5.10/drivers/dma-buf/ |
| D | Kconfig | 5 bool "Explicit Synchronization Framework"
9 The Sync File Framework adds explicit synchronization via
|
| /kernel/linux/linux-5.10/include/uapi/rdma/ |
| D | cxgb4-abi.h | 97 __u32 reserved; /* explicit padding */
108 __u32 reserved; /* explicit padding (optional for i386) */
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/progs/ |
| D | btf_dump_test_case_padding.c | 4 * BTF-to-C dumper tests for implicit and explicit padding between fields and
50 /* 32 bit of implicit padding here, which algo will make explicit */
|
| /kernel/linux/linux-5.10/drivers/acpi/acpica/ |
| D | utstrtoul64.c | 24 * 2) Runtime "Explicit conversion" as defined in the ACPI specification.
32 * interpreter - Implicit and explicit conversions, GPE method names
40 * acpi_gbl_integer_byte_width is used to set the 32/64 bit limit for explicit
51 * support (explicit/implicit) for octal string conversions.
246 * an "explicit conversion" by the ACPI specification. The
|
| D | exconvrt.c | 93 * Explicit conversion is used only by to_integer. in acpi_ex_convert_to_integer()
368 * and explicit conversions and related rules.
446 * Explicit conversion from the to_decimal_string ASL operator. in acpi_ex_convert_to_string()
484 * Explicit conversion from the to_hex_string ASL operator. in acpi_ex_convert_to_string()
523 /* Emit 0x prefix for explicit/implicit hex conversion */ in acpi_ex_convert_to_string()
608 "Explicit operator, will store (%s) over existing type (%s)\n", in acpi_ex_convert_to_target_type()
|
| /kernel/linux/linux-5.10/Documentation/arm/ |
| D | cluster-pm-race-avoidance.rst | 153 a) an explicit hardware power-up operation, resulting
189 The CPU remains in this state until an explicit policy decision
197 explicit policy decision
309 a) an explicit hardware power-up operation, resulting
398 a) an explicit hardware power-up operation,
|
| /kernel/linux/linux-5.10/drivers/nvdimm/ |
| D | dimm.c | 36 * The locked status bit reflects explicit status codes from the in nvdimm_probe()
58 * otherwise the locked indication is determined by explicit in nvdimm_probe()
|
| /kernel/linux/linux-5.10/include/trace/events/ |
| D | block.h | 485 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
487 TP_ARGS(q, depth, explicit),
506 * @explicit: whether this was an explicit unplug, or one from schedule()
513 TP_PROTO(struct request_queue *q, unsigned int depth, bool explicit),
515 TP_ARGS(q, depth, explicit)
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | rpmsg.rst | 96 its length (in bytes), and an explicit destination address.
121 its length (in bytes), and explicit source and destination addresses.
160 its length (in bytes), and an explicit destination address.
182 its length (in bytes), and explicit source and destination addresses.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_atomic_uapi.c | 251 * implicit or explicit fencing.
254 * via explicit fencing interfaces on the atomic ioctl. In that case it will
260 * This way explicit fencing can be used to overrule implicit fencing, which is
261 * important to make explicit fencing use-cases work: One example is using one
263 * clamp rendering to the refresh rate of the slower screen, whereas explicit
265 * driver allows obeys both implicit and explicit fences for plane updates, then
266 * it will break all the benefits of explicit fencing.
1036 * DOC: explicit fencing properties
1038 * Explicit fencing allows userspace to control the buffer synchronization
1049 * whereas explicit fencing is what Android wants.
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/xen/ |
| D | trace_types.h | 6 XEN_MC_FL_NONE, /* explicit flush */
|