| /OK3568_Linux_fs/kernel/Documentation/ |
| H A D | memory-barriers.txt | 16 meant as a guide to using the various memory barriers provided by Linux, but
31 (2) to provide a guide as to how to use the barriers that are available.
51 (*) What are memory barriers?
54 - What may not be assumed about memory barriers?
55 - Data dependency barriers (historical).
59 - Read memory barriers vs load speculation.
62 (*) Explicit kernel barriers.
65 - CPU memory barriers.
67 (*) Implicit kernel memory barriers.
78 (*) Where are memory barriers needed?
[all …]
|
| H A D | atomic_t.txt | 160 ORDERING (go read memory-barriers.txt first)
188 The barriers:
193 ordering inherent to the op. These barriers act almost like a full smp_mb():
201 These helper barriers exist because architectures have varying implicit
203 provide full ordered atomics and these barriers are no-ops.
|
| H A D | atomic_bitops.txt | 70 the same barriers as for atomic_t are used, see atomic_t.txt.
|
| /OK3568_Linux_fs/external/xserver/Xi/ |
| H A D | xibarriers.c | 95 struct xorg_list barriers; member
334 xorg_list_for_each_entry(c, &cs->barriers, entry) { in barrier_find_nearest()
418 if (xorg_list_is_empty(&cs->barriers) || IsFloating(dev)) in input_constrain_cursor()
483 xorg_list_for_each_entry(c, &cs->barriers, entry) { in input_constrain_cursor()
632 xorg_list_add(&ret->entry, &cs->barriers); in CreatePointerBarrierClient()
929 xorg_list_init(&cs->barriers); in XIBarrierInit()
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-bsp/flashrom/flashrom/ |
| H A D | 0001-hwaccess-use-__asm__-as-is-done-elsewhere.patch | 29 …ps://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/memory-barriers.txt
38 * use the strongest hardware memory barriers that exist on Sparc V9. */
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | circular-buffers.rst | 15 (2) Memory barriers for when the producer and the consumer of objects in the
29 (*) Using memory barriers with circular buffers.
134 Using memory barriers with circular buffers
137 By using memory barriers in conjunction with circular buffers, you can avoid
236 See also Documentation/memory-barriers.txt for a description of Linux's memory
|
| H A D | atomic_ops.rst | 86 Some architectures may choose to use the volatile keyword, barriers, or
156 and never changed later, so that memory barriers are not needed::
179 Don't even -think- about doing this without proper use of memory barriers,
200 require any explicit memory barriers. They need only perform the
213 include explicit memory barriers that are performed before and after
268 atomic_xchg must provide explicit memory barriers around the operation. ::
277 atomic_cmpxchg must provide explicit memory barriers around the operation,
292 atomic_add_unless must provide explicit memory barriers around the
392 memory barriers in kfree_skb() that exposed the atomic_t memory barrier
510 If explicit memory barriers are required around {set,clear}_bit() (which do
[all …]
|
| H A D | refcount-vs-atomic.rst | 22 memory-barriers.txt and atomic_t.txt provide more background to the
31 please consult memory-barriers.txt document.
69 barriers, but rely on CPU not to speculate on stores. This is only
|
| H A D | local_ops.rst | 31 removing the LOCK prefix and memory barriers normally required to synchronize
129 between CPUs, explicit ``smp_wmb()`` and ``smp_rmb()`` memory barriers must be used
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | lockdep.rst | 57 Use explicit check expression "c", and omit all barriers
62 Return the value of the pointer and omit all barriers,
98 barriers and compiler constraints, it generates better code than do the
|
| H A D | arrayRCU.rst | 72 which includes any memory barriers required on whatever architecture
118 that it may later safely be dereferenced -- memory barriers are
|
| H A D | listRCU.rst | 8 is that all of the required memory barriers are included for you in
124 insert the read-side memory barriers that are required on DEC Alpha CPUs.
199 The **_rcu()** list-manipulation primitives add memory barriers that are needed on
332 need additional memory barriers to ensure that the list_add_rcu() was really
|
| /OK3568_Linux_fs/kernel/Documentation/staging/ |
| H A D | index.rst | 53 .. include:: ../memory-barriers.txt
|
| /OK3568_Linux_fs/kernel/tools/memory-model/litmus-tests/ |
| H A D | R+fencembonceonces.litmus | 8 * propagation delays. Note that weakening either of the barriers would
|
| H A D | SB+fencembonceonces.litmus | 6 * This litmus test demonstrates that full memory barriers suffice to
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/ |
| H A D | vcpu-requests.rst | 177 [memory-barriers]_.
180 the memory barriers, allowing this requirement to be handled internally by
203 This solution also requires memory barriers to be placed carefully in both
204 the requesting thread and the receiving VCPU. With the memory barriers we
306 .. [memory-barriers] Documentation/memory-barriers.txt
|
| /OK3568_Linux_fs/kernel/drivers/staging/vc04_services/interface/ |
| H A D | TODO | 53 7) Review and comment memory barriers
55 There is a heavy use of memory barriers in this driver, it would be very
|
| /OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/arm64/ |
| H A D | legacy_instructions.txt | 42 它是那些构架中正在被淘汰的指令，如 CP15 barriers（隔离指令），的默认处理方式。
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | ext4.rst | 56 note that ext4 enables write barriers by default, while ext3 does
57 not enable write barriers by default. So it is useful to use
58 explicitly specify whether barriers are enabled or not when via the
59 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
199 This enables/disables the use of write barriers in the jbd code.
201 which can support barriers, and if jbd gets an error on a barrier
202 write, it will disable again with a warning. Write barriers enforce
205 battery-backed in one way or another, disabling barriers may safely
207 also be used to enable or disable barriers, for consistency with other
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 344 * - 'Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers'
347 pointer sanitation and usercopy LFENCE barriers.
348 * - 'Mitigation: usercopy/swapgs barriers and __user pointer sanitization'
350 pointer sanitation, usercopy LFENCE barriers, and swapgs LFENCE
351 barriers.
456 For the swapgs variant of Spectre variant 1, LFENCE barriers are
458 barriers are done by the FENCE_SWAPGS_KERNEL_ENTRY and
|
| /OK3568_Linux_fs/kernel/tools/memory-model/Documentation/ |
| H A D | recipes.txt | 287 Write and read memory barriers
347 weaker barriers.
477 first. Preserving order requires nothing less than full barriers:
495 values of 0, but providing both full barriers as shown above prevents
517 "if (@cond)". The full barriers prevent the undesirable outcome where
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 22 safe (spinlocks, mutexes, memory barriers, etc.) are designed to prevent
38 primitives act as memory barriers - they are explicitly written to do so -
|
| /OK3568_Linux_fs/kernel/Documentation/arm64/ |
| H A D | legacy_instructions.rst | 27 instructions, .e.g., CP15 barriers
|
| /OK3568_Linux_fs/kernel/Documentation/arm/ |
| H A D | kernel_user_helpers.rst | 167 - This routine already includes memory barriers as needed.
263 - This routine already includes memory barriers as needed.
|
| /OK3568_Linux_fs/kernel/tools/memory-model/ |
| H A D | README | 187 references, memory barriers, atomic read-modify-write operations,
196 memory barriers, atomic read-modify-write operations, and RCU.
|