Searched full:atomic (Results 1 – 25 of 172) sorted by relevance
1234567
| /Documentation/ |
| D | atomic_bitops.txt | 2 Atomic bitops
5 While our bitmap_{}() functions are non-atomic, we have a number of operations
6 operating on single bits in a bitmap that are atomic.
18 RMW atomic operations without return value:
23 RMW atomic operations with return value:
33 All RMW atomic operations have a '__' prefixed variant which is non-atomic.
39 Non-atomic ops:
67 Since a platform only has a single means of achieving atomic operations
|
| D | atomic_t.txt | 2 On atomic types (atomic_t atomic64_t and atomic_long_t).
4 The atomic type provides an interface to the architecture's means of atomic
5 RMW operations between CPUs (atomic operations on MMIO are not supported and
20 RMW atomic operations:
67 Therefore, an explicitly unsigned variant of the atomic ops is strictly
91 C Atomic-RMW-ops-are-atomic-WRT-atomic_set
118 The obvious case where this is not so is when we need to implement atomic ops
155 All these operations are SMP atomic; that is, the operations (for a single
156 atomic variable) can be fully ordered and no intermediate state is lost or
192 only apply to the RMW atomic ops and can be used to augment/upgrade the
[all …]
|
| /Documentation/litmus-tests/ |
| D | README | 12 atomic (/atomic directory)
15 Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus
16 Test that an atomic RMW followed by a smp_mb__after_atomic() is
20 Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus
21 Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
| /Documentation/core-api/ |
| D | local_ops.rst | 5 Semantics and Behavior of Local Atomic Operations
11 This document explains the purpose of the local atomic operations, how
26 Purpose of local atomic operations
29 Local atomic operations are meant to provide fast and highly reentrant per CPU
30 counters. They minimize the performance cost of standard atomic operations by
34 Having fast per CPU atomic counters is interesting in many cases: it does not
39 Local atomic operations only guarantee variable modification atomicity wrt the
50 It can be done by slightly modifying the standard atomic operations: only
63 Rules to follow when using local atomic operations
82 "``long``", aligned, variables are always atomic. Since no memory
[all …]
|
| D | refcount-vs-atomic.rst | 12 implementation from lib/refcount.c uses atomic operations underneath,
23 memory ordering in general and for atomic operations specifically.
36 each ``atomic_*()`` and ``refcount_*()`` operation is atomic and instructions
131 * no atomic counterpart --> refcount_add_not_zero()
147 * no atomic counterpart --> refcount_add_not_zero_acquire()
172 * no atomic counterpart --> refcount_dec_if_one()
|
| /Documentation/arch/xtensa/ |
| D | atomctl.rst | 2 Atomic Operation Control (ATOMCTL) Register
5 We Have Atomic Operation Control (ATOMCTL) Register.
10 can do Atomic Transactions to the memory internally.
13 can do Atomic Transactions itself.
21 Memory controller we let it to the atomic operations internally while
31 don't support atomic RCW memory transactions and will likely want to
|
| /Documentation/litmus-tests/atomic/ |
| D | Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 1 C Atomic-RMW-ops-are-atomic-WRT-atomic_set
6 * Test that atomic_set() cannot break the atomicity of atomic RMWs.
|
| D | Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus | 1 C Atomic-RMW+mb__after_atomic-is-stronger-than-acquire
6 * Test that an atomic RMW followed by a smp_mb__after_atomic() is
|
| /Documentation/driver-api/ |
| D | basics.rst | 96 .. kernel-doc:: include/linux/atomic/atomic-instrumented.h
99 .. kernel-doc:: include/linux/atomic/atomic-arch-fallback.h
102 .. kernel-doc:: include/linux/atomic/atomic-long.h
|
| /Documentation/bpf/ |
| D | clang-notes.rst | 29 Atomic operations
32 Clang can generate atomic instructions by default when ``-mcpu=v3`` is
33 enabled. If a lower version for ``-mcpu`` is set, the only atomic instruction
|
| /Documentation/livepatch/ |
| D | cumulative-patches.rst | 2 Atomic Replace & Cumulative Patches
13 An elegant solution comes with the feature called "Atomic Replace". It allows
20 The atomic replace can be enabled by setting "replace" flag in struct klp_patch,
50 The atomic replace allows:
|
| /Documentation/bpf/standardization/ |
| D | instruction-set.rst | 142 * atomic32: includes 32-bit atomic operation instructions (see `Atomic operations`_).
143 * atomic64: includes atomic32, plus 64-bit atomic operation instructions.
593 ATOMIC 6 atomic operations `Atomic operations`_
649 Atomic operations
652 Atomic operations are operations that operate on memory and can not be
656 All atomic operations supported by BPF are encoded as store operations
657 that use the ``ATOMIC`` mode modifier as follows:
659 * ``{ATOMIC, W, STX}`` for 32-bit operations, which are
661 * ``{ATOMIC, DW, STX}`` for 64-bit operations, which are
663 * 8-bit and 16-bit wide atomic operations are not supported.
[all …]
|
| /Documentation/timers/ |
| D | timers-howto.rst | 17 code in an atomic context?" This should be followed closely by "Does
18 it really need to delay in atomic context?" If so...
20 ATOMIC CONTEXT:
38 NON-ATOMIC CONTEXT:
|
| /Documentation/locking/ |
| D | pi-futex.rst | 9 calls - just pure fast atomic ops in userspace.
82 futexes.) Userspace uses atomic ops to lock/unlock these mutexes without
90 If the lock-acquire fastpath fails, [i.e. an atomic transition from 0 to
105 TID -> 0 atomic transition of the futex value], then no kernel work is
|
| /Documentation/gpu/ |
| D | todo.rst | 44 Convert existing KMS drivers to atomic modesetting
47 3.19 has the atomic modeset interfaces and helpers, so drivers can now be
49 really want an atomic modeset interface, so this is all about the bright
52 There is a conversion guide for atomic [1]_ and all you need is a GPU for a
53 non-converted driver. The "Atomic mode setting design overview" series [2]_
58 do by directly using the new atomic helper driver callbacks.
60 .. [1] https://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html
72 it's not consistently used. This should be fixed, preferably in the atomic
74 helper should also be moved from drm_plane_helper.c to the atomic helpers, to
104 Convert early atomic drivers to async commit helpers
[all …]
|
| D | vkms.rst | 183 Atomic Check using eBPF
186 Atomic drivers have lots of restrictions which are not exposed to userspace in
188 inquiry about these limits through the atomic IOCTL, possibly using the
191 we could add support for eBPF to validate any kind of atomic state, and
|
| D | drm-kms.rst | 141 at the encoder level. Atomic drivers can leave out all the encoder callbacks to
181 which are especially important for the atomic IOCTL (see `Atomic Mode
194 Atomic Mode Setting
237 Atomic provides transactional modeset (including planes) updates, but a
250 - Lastly, for backwards compatibility and to support all use-cases, atomic
256 Taken all together there's two consequences for the atomic design:
267 - An atomic update is assembled and validated as an entirely free-standing pile
274 Locking of atomic state structures is internally using :c:type:`struct
291 Atomic Mode Setting Function Reference
300 Atomic Mode Setting IOCTL and UAPI Functions
|
| D | introduction.rst | 159 * `Embrace the Atomic (Display) Age <https://www.youtube.com/watch?v=LjiB_JeDn2M>`_ - Simona Vetter…
160 * `Anatomy of an Atomic KMS Driver <https://www.youtube.com/watch?v=lihqR9sENpc>`_ - Laurent Pincha…
161 * `Atomic Modesetting for Drivers <https://www.youtube.com/watch?v=kl9suFgbTc8>`_ - Simona Vetter (…
172 * `Atomic mode setting design overview, part 1 <https://lwn.net/Articles/653071/>`_ - Simona Vetter…
173 * `Atomic mode setting design overview, part 2 <https://lwn.net/Articles/653466/>`_ - Simona Vetter…
|
| /Documentation/core-api/wrappers/ |
| D | atomic_t.rst | 6 Atomic types
|
| D | atomic_bitops.rst | 6 Atomic bitops
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi | 18 latency, should not be considered for atomic mode of operation,
35 SCMI instance <n> is capable of atomic mode of operation.
|
| D | sysfs-fs-erofs | 16 readahead on atomic contexts only.
|
| /Documentation/translations/zh_CN/ |
| D | glossary.rst | 16 * atomic: 原子的，一般指不可中断的极小的临界区操作。
|
| /Documentation/networking/devlink/ |
| D | devlink-region.rst | 35 snapshot. Direct read requests are not atomic. In particular a read request
36 of size 256 bytes or larger will be split into multiple chunks. If atomic
|
| /Documentation/gpu/amdgpu/display/ |
| D | mpo-overview.rst | 24 Multiplane Overlay is only available using the DRM atomic model. The atomic
60 limit of 4 planes across all CRTCs. Atomic commits will be rejected for display
70 Atomic commits will be rejected for commits which do not follow these
167 - ``kms_plane_multiple@atomic-pipe-*-tiling-``
|
1234567