| /linux/tools/testing/selftests/rseq/ |
| H A D | rseq-abi.h | 86 * kernel. Read by user-space with single-copy atomicity
99 * Read by user-space with single-copy atomicity semantics. This
127 * atomicity semantics. This field should only be updated by the
173 * user-space with single-copy atomicity semantics. This field should
181 * user-space with single-copy atomicity semantics. This field should
|
| /linux/include/uapi/linux/ |
| H A D | rseq.h | 105 * kernel. Read by user-space with single-copy atomicity
118 * Read by user-space with single-copy atomicity semantics. This
146 * atomicity semantics. This field should only be updated by the
169 * user-space with single-copy atomicity semantics. This field should
177 * user-space with single-copy atomicity semantics. This field should
|
| H A D | virtio_mmio.h | 136 /* Configuration atomicity value */
|
| /linux/arch/arc/include/asm/ |
| H A D | smp.h | 80 * Originally Interrupts had to be disabled around code to guarantee atomicity.
88 * (2) In a SMP setup, the LLOCK/SCOND atomicity across CPUs needs to be
91 * disabling for atomicity.
|
| /linux/Documentation/litmus-tests/atomic/ |
| H A D | Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 6 * Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
| /linux/arch/arm/include/asm/ |
| H A D | arch_gicv3.h | 168 * GICR_TYPER is an ID register and doesn't need atomicity.
194 * GITS_TYPER is an ID register and doesn't need atomicity.
|
| /linux/Documentation/arch/arm/ |
| H A D | vlocks.rst | 15 vlocks make use of the atomicity provided by the memory system for
73 atomicity is used to pick the winner. This avoids the need for a static
|
| H A D | swp_emulation.rst | 25 atomicity. If your system does not implement a global monitor, this option can
|
| /linux/drivers/net/wireless/mediatek/mt7601u/ |
| H A D | mt7601u.h | 145 * @vendor_req_mutex: protects @vend_buf, ensures atomicity of read/write
147 * @reg_atomic_mutex: ensures atomicity of indirect register accesses
|
| /linux/arch/arm/mach-versatile/ |
| H A D | spc.c | 123 * working. Locking must be provided by the caller to ensure atomicity.
148 * working. Locking must be provided by the caller to ensure atomicity.
202 * working. Locking must be provided by the caller to ensure atomicity.
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_timeline_types.h | 41 * from the intel_context caller plus internal atomicity.
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 60 - Multicopy atomicity.
669 the CPU containing it. See the section on "Multicopy atomicity" for
890 to the CPU containing it. See the section on "Multicopy atomicity"
932 (*) Control dependencies do -not- provide multicopy atomicity. If you
946 other types of barriers, albeit without multicopy atomicity. An acquire
1370 MULTICOPY ATOMICITY
1373 Multicopy atomicity is a deeply intuitive notion about ordering that is
1377 support of full multicopy atomicity would rule out valuable hardware
1378 optimizations, so a weaker form called ``other multicopy atomicity''
1381 weaker form, but for brevity will call it simply ``multicopy atomicity''.
[all …]
|
| /linux/drivers/leds/ |
| H A D | TODO | 9 * Review atomicity requirements in LED subsystem
|
| /linux/include/linux/ |
| H A D | spinlock_up.h | 20 * No atomicity anywhere, we are on UP. However, we still need
|
| /linux/Documentation/litmus-tests/ |
| H A D | README | 21 Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
| /linux/Documentation/filesystems/ |
| H A D | nilfs2.rst | 71 conserve atomicity. This will improve synchronous
256 to ensure atomicity of updates.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-integrity.rst | 12 To guarantee write atomicity, the dm-integrity target uses journal, it
82 journal and atomicity is guaranteed. In case of crash,
|
| /linux/arch/sh/ |
| H A D | Kconfig | 616 This enables support for gUSA (general UserSpace Atomicity).
624 atomicity implementations exist.
|
| /linux/kernel/sched/ |
| H A D | stats.h | 10 * Expects runqueue lock to be held for atomicity of update
22 * Expects runqueue lock to be held for atomicity of update
|
| /linux/include/soc/arc/ |
| H A D | mcip.h | 114 * Callers need to lock to ensure atomicity
|
| /linux/fs/9p/ |
| H A D | v9fs_vfs.h | 19 * you lose the atomicity of file open
|
| /linux/include/asm-generic/ |
| H A D | rwonce.h | 41 * atomicity. Note that this may result in tears!
|
| /linux/include/asm-generic/bitops/ |
| H A D | instrumented-non-atomic.h | 70 * non-atomicity of the writer is sufficient may be reasonable in __instrument_read_write_bitop()
|
| /linux/include/media/ |
| H A D | v4l2-cci.h | 95 * Note this uses read-modify-write to update the bits, atomicity with regards
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | btt.rst | 12 will do exactly this. However, they do not provide any atomicity guarantees.
126 The BTT provides sector atomicity by making every write an "allocating write",
|