/linux/arch/powerpc/perf/ |
H A D | hv-gpci.c | 221 * 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/tools/memory-model/Documentation/ |
H A D | ordering.txt | 13 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/arch/riscv/include/asm/vendor_extensions/ |
H A D | mips.h | 28 * any subsequent instructions to execute. 30 * allowing any subsequent instructions to fetch.
|
/linux/Documentation/filesystems/spufs/ |
H A D | spufs.rst | 179 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/tools/lib/api/fs/ |
H A D | fs.h | 28 * subsequent calls. 31 * subsequent calls.
|
/linux/drivers/bus/fsl-mc/ |
H A D | dpmcp.c | 16 * @token: Returned token; use in subsequent API calls 23 * portal; this token must be used in all subsequent commands for
|
H A D | dpbp.c | 16 * @token: Returned token; use in subsequent API calls 23 * portal; this token must be used in all subsequent commands for
|
H A D | dpcon.c | 16 * @token: Returned token; use in subsequent API calls 23 * portal; this token must be used in all subsequent commands for
|
/linux/arch/arm64/kernel/pi/ |
H A D | relocate.c | 36 * address entry encodes 1 relocation. The subsequent bitmap entries in relocate_kernel() 37 * encode up to 63 relocations each, at subsequent offsets following in relocate_kernel()
|
/linux/lib/ |
H A D | cmdline.c | 40 * 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
|
H A D | textsearch.c | 43 * 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/Documentation/userspace-api/media/v4l/ |
H A D | func-select.rst | 63 or ``writefds``, but subsequent :ref:`VIDIOC_DQBUF <VIDIOC_QBUF>` 69 a subsequent :c:func:`read()` call, which also attempts to start
|
/linux/arch/powerpc/include/asm/ |
H A D | barrier.h | 95 * Prevent execution of subsequent instructions until preceding branches have 112 * access or data transfer caused by subsequent instructions is
|
/linux/include/uapi/linux/ |
H A D | falloc.h | 83 * subsequent writes to that range do not require further changes to the file 84 * mapping metadata. This flag is beneficial for subsequent pure overwriting
|
H A D | wireguard.h | 62 * not fit within a single message. So, subsequent peers will be sent 130 * of a peer, it likely should not be specified in subsequent fragments.
|
H A D | dma-buf.h | 157 * this inserts the sync_file as a read-only fence. Any subsequent 162 * write fence. All subsequent implicitly synchronized access to
|
/linux/arch/s390/include/asm/ |
H A D | sclp.h | 158 u16 length; /* Length of Subsequent Data (up to 4K – SCLP header */ 159 u8 data[]; /* Subsequent Data passed verbatim to SCLP ET 24 */
|
/linux/Documentation/tools/rtla/ |
H A D | common_options.rst | 62 the order they are provided. If any action fails, subsequent actions in the list 105 they are provided. If any action fails, subsequent actions in the list will not be
|
/linux/arch/powerpc/kernel/ |
H A D | eeh_event.c | 162 * On PowerNV platform, we might have subsequent coming events 163 * is part of the former one. For that case, those subsequent
|
/linux/include/linux/ |
H A D | entry-common.h | 54 * subsequent functions can be instrumented. 109 * subsequent functions can be instrumented.
|
/linux/drivers/net/ethernet/broadcom/bnxt/ |
H A D | bnxt_hwrm.c | 131 * 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/arch/arm64/kernel/probes/ |
H A D | kprobes_trampoline.S | 15 * kretprobe_brk_handler(), and no subsequent instructions will
|
/linux/tools/memory-model/litmus-tests/ |
H A D | S+fencewmbonceonce+poacquireonce.litmus | 7 * store against a subsequent store?
|
/linux/drivers/net/ipa/ |
H A D | ipa_qmi.c | 43 * subsequent boots. The modem expects to receive a final INIT_COMPLETE 61 * - On subsequent modem boots, everything is ready when: 120 * initial boot, non-zero (true) for a subsequent (SSR) boot. 478 * subsequent boots. The INIT_COMPLETE indication message is in ipa_qmi_setup()
|
/linux/drivers/soc/fsl/dpio/ |
H A D | dpio.c | 23 * @token: Returned token; use in subsequent API calls 30 * portal; this token must be used in all subsequent commands for
|