Home
last modified time | relevance | path

Searched full:subsequent (Results 1 – 25 of 1124) sorted by relevance

12345678910>>...45

/Linux-v6.6/arch/powerpc/perf/
Dhv-gpci.c221 * returned. To handle that, we need to make subsequent requests in processor_bus_topology_show()
223 * Below loop do subsequent hcalls with next starting index and add it in processor_bus_topology_show()
234 * element and add 1 to make subsequent hcalls. in processor_bus_topology_show()
289 * returned. To handle that, we need to take subsequent requests in processor_config_show()
291 * Below loop do subsequent hcalls with next starting index and add it in processor_config_show()
302 * element and add 1 to subsequent hcalls. in processor_config_show()
357 * returned. To handle that, we need to take subsequent requests in affinity_domain_via_virtual_processor_show()
359 * Below loop do subsequent hcalls with next secondary index and add it in affinity_domain_via_virtual_processor_show()
370 * last array element as subsequent starting index, and use secondary index in affinity_domain_via_virtual_processor_show()
371 * value in the last array element plus 1 as subsequent secondary index. in affinity_domain_via_virtual_processor_show()
[all …]
/Linux-v6.6/tools/arch/ia64/include/asm/
Dbarrier.h21 * and "subsequent" refer to program order; "visible" means that all
26 * like regions are visible before any subsequent
31 * accesses are visible before all subsequent
/Linux-v6.6/tools/memory-model/Documentation/
Dordering.txt13 subsequent operations.
17 of the CPU's subsequent accesses, depending on the subcategory
68 accesses against all subsequent accesses from the viewpoint of all CPUs.
158 ordering subsequent to an unordered RMW atomic operation.
160 o smp_mb__after_spinlock(), which provides full ordering subsequent
165 subsequent to an srcu_read_unlock().
322 operations order their own load against all of the CPU's subsequent
333 improves upon smp_rmb() by ordering against subsequent stores as well
334 as against subsequent loads.
391 of the CPU's subsequent memory accesses whose address has been calculated
[all …]
/Linux-v6.6/arch/ia64/include/asm/
Dbarrier.h19 * and "subsequent" refer to program order; "visible" means that all
24 * like regions are visible before any subsequent
29 * accesses are visible before all subsequent
/Linux-v6.6/Documentation/filesystems/spufs/
Dspufs.rst179 subsequent reads from the same file descriptor will result in
182 subsequent read operations will return zero bytes and a new file
189 buffer. Subsequent writes to the same file descriptor overwrite
249 subsequent read operations will return zero bytes and a new file
256 buffer. Subsequent writes to the same file descriptor overwrite
/Linux-v6.6/tools/lib/api/fs/
Dfs.h28 * subsequent calls.
31 * subsequent calls.
/Linux-v6.6/fs/ntfs/
Dbitmap.c105 /* If we are not in the last page, deal with all subsequent pages. */ in __ntfs_bitmap_set_bits_in_run()
166 ntfs_error(vi->i_sb, "Failed to map subsequent page (error " in __ntfs_bitmap_set_bits_in_run()
170 ntfs_error(vi->i_sb, "Failed to map subsequent page (error " in __ntfs_bitmap_set_bits_in_run()
/Linux-v6.6/drivers/bus/fsl-mc/
Ddpmcp.c16 * @token: Returned token; use in subsequent API calls
23 * portal; this token must be used in all subsequent commands for
Ddpbp.c16 * @token: Returned token; use in subsequent API calls
23 * portal; this token must be used in all subsequent commands for
Ddpcon.c16 * @token: Returned token; use in subsequent API calls
23 * portal; this token must be used in all subsequent commands for
/Linux-v6.6/drivers/dma/fsl-dpaa2-qdma/
Ddpdmai.c56 * @token: Returned token; use in subsequent API calls
63 * portal; this token must be used in all subsequent commands for
123 * @token: Returned token; use in subsequent API calls
133 * portal; this token must be used in all subsequent calls to
/Linux-v6.6/lib/
Dcmdline.c40 * Read an int from an option string; if available accept a subsequent
48 * 1 - int found, no subsequent comma
49 * 2 - int found including a subsequent comma
Dtextsearch.c43 * textsearch_next() to fetch subsequent occurrences. A state variable
71 * no match was found. Subsequent occurrences can be found by calling
226 * Call textsearch_next() to retrieve subsequent matches.
/Linux-v6.6/Documentation/userspace-api/media/v4l/
Dfunc-select.rst63 or ``writefds``, but subsequent :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>`
69 a subsequent :c:func:`read()` call, which also attempts to start
/Linux-v6.6/arch/powerpc/include/asm/
Dbarrier.h95 * Prevent execution of subsequent instructions until preceding branches have
112 * access or data transfer caused by subsequent instructions is
/Linux-v6.6/arch/s390/include/asm/
Dsclp.h121 u16 length; /* Length of Subsequent Data (up to 4K – SCLP header */
122 u8 data[]; /* Subsequent Data passed verbatim to SCLP ET 24 */
/Linux-v6.6/include/linux/
Dentry-common.h95 * disabled. The subsequent functions can be instrumented.
110 * subsequent functions can be instrumented.
154 * subsequent functions can be instrumented.
334 * state is correct and the subsequent functions can be instrumented.
/Linux-v6.6/Documentation/admin-guide/hw-vuln/
Dsrso.rst17 to predict the target of a subsequent RET instruction.
22 control the speculative target of a subsequent kernel RET, potentially
/Linux-v6.6/tools/memory-model/litmus-tests/
DS+fencewmbonceonce+poacquireonce.litmus7 * store against a subsequent store?
/Linux-v6.6/arch/powerpc/kernel/
Deeh_event.c162 * On PowerNV platform, we might have subsequent coming events
163 * is part of the former one. For that case, those subsequent
/Linux-v6.6/include/uapi/linux/
Dwireguard.h62 * not fit within a single message. So, subsequent peers will be sent
126 * of a peer, it likely should not be specified in subsequent fragments.
/Linux-v6.6/Documentation/devicetree/bindings/hwmon/
Dnsa320-mcu.txt2 the Zyxel NSA 320 and several subsequent models.
/Linux-v6.6/Documentation/ABI/testing/
Dprocfs-attr-exec7 after a subsequent exec() call.
/Linux-v6.6/drivers/net/ethernet/broadcom/bnxt/
Dbnxt_hwrm.c131 * Set the timeout associated with the request for subsequent calls to
154 * Sets the GFP allocation flags associated with the request for subsequent
170 * an assignment of new_req to req. Subsequent calls to HWRM API functions,
182 * reference the new request and use it in lieu of req during subsequent
237 * ctx flags can be used by the callers to instruct how the subsequent
261 * hwrm_req_drop(). The caller taking ownership implies that a subsequent
/Linux-v6.6/drivers/soc/fsl/dpio/
Ddpio.c23 * @token: Returned token; use in subsequent API calls
30 * portal; this token must be used in all subsequent commands for

12345678910>>...45