Searched refs:primitives (Results 1 – 25 of 50) sorted by relevance
12
/Linux-v5.4/Documentation/RCU/ |
D | checklist.txt | 24 read-side primitives is critically important. 56 rcu_read_lock() and friends? These primitives are needed 82 primitives to add, remove, and replace elements on 99 appear atomic, as will individual atomic primitives. 102 of multiple atomic primitives. 145 various "_rcu()" list-traversal primitives, such 149 primitives. This is particularly useful in code that 156 list-traversal primitives can substitute for a good 160 and list_add_rcu() primitives must be used in order 172 The list_replace_rcu() and hlist_replace_rcu() primitives [all …]
|
D | lockdep.txt | 10 In addition, RCU provides the following primitives that check lockdep's 24 checking of rcu_dereference() primitives: 100 and RCU list-/tree-traversal primitives, which do not (yet) check for 102 versions of these primitives might be created.
|
D | listRCU.rst | 74 become list_for_each_entry_rcu(). The _rcu() list-traversal primitives 149 The list_del(), list_add(), and list_add_tail() primitives have been 151 The _rcu() list-manipulation primitives add memory barriers that are
|
D | rcu_dereference.txt | 4 the similar primitives without worries. Dereferencing (prefix "*"), 11 o You must use one of the rcu_dereference() family of primitives 15 Without one of the rcu_dereference() primitives, compilers 148 kernel's wide array of primitives that cause code to
|
D | whatisRCU.txt | 231 the _rcu list-manipulation primitives such as list_add_rcu(). 293 primitives, such as list_for_each_entry_rcu(). 340 sychronize_rcu() and call_rcu() primitives used are the same for all three 341 flavors. However for protection (on the reader side), the primitives used vary 448 rcu_assign_pointer() primitives from interfering with each other. 560 in terms of familiar locking primitives, and another that more closely 576 familiar locking primitives. Its overhead makes it a non-starter for
|
D | rcu.rst | 60 "synchronize_srcu", and the other RCU primitives. Or grab one
|
/Linux-v5.4/drivers/staging/clocking-wizard/ |
D | TODO | 5 refactoring of the clk primitives: https://lkml.org/lkml/2014/9/5/766)
|
/Linux-v5.4/Documentation/devicetree/bindings/mailbox/ |
D | nvidia,tegra186-hsp.txt | 4 together. It provides a set of hardware synchronization primitives for 6 protocols can use hardware synchronization primitives, when operating between
|
/Linux-v5.4/tools/testing/selftests/powerpc/ |
D | Makefile | 24 primitives \
|
/Linux-v5.4/include/linux/ |
D | intel_rapl.h | 64 u64 primitives[NR_RAPL_PRIMITIVES]; member
|
/Linux-v5.4/Documentation/driver-api/usb/ |
D | dma.rst | 44 For those specific cases, USB has primitives to allocate less expensive 55 Most drivers should **NOT** be using these primitives; they don't need 135 calls (where the underlying DMA primitives have changed), most of them can
|
/Linux-v5.4/Documentation/core-api/ |
D | genericirq.rst | 121 primitives referenced by the assigned chip descriptor structure. 181 The helper functions call the chip primitives and are used by the 277 The simple flow handler does not call any handler/chip primitives. 365 These primitives are strictly intended to mean what they say: ack means 384 chip primitives. The per-irq structure is protected via desc->lock, by
|
/Linux-v5.4/Documentation/devicetree/bindings/firmware/ |
D | nvidia,tegra210-bpmp.txt | 16 - reg: physical base address and length for HW synchornization primitives
|
/Linux-v5.4/Documentation/process/ |
D | volatile-considered-harmful.rst | 21 Like volatile, the kernel primitives which make concurrent access to data 38 primitives act as memory barriers - they are explicitly written to do so -
|
/Linux-v5.4/Documentation/driver-api/ |
D | i2c.rst | 35 operations, either using I2C primitives or by issuing SMBus commands to
|
/Linux-v5.4/Documentation/ |
D | atomic_t.txt | 183 Fully ordered primitives are ordered against everything prior and everything 202 ordering on their SMP atomic primitives. For example our TSO architectures
|
D | speculation.txt | 71 primitives.
|
/Linux-v5.4/tools/testing/selftests/futex/ |
D | README | 11 primitives. These can be used as is in user applications or can serve as
|
/Linux-v5.4/kernel/ |
D | Kconfig.preempt | 64 various locking primitives (spinlocks, rwlocks, etc.) with
|
/Linux-v5.4/tools/memory-model/ |
D | README | 158 relations on the locking primitives. 200 operations, locking primitives, and RCU is not provided.
|
/Linux-v5.4/tools/testing/selftests/bpf/prog_tests/ |
D | core_reloc.c | 235 PRIMITIVES_CASE(primitives),
|
/Linux-v5.4/drivers/crypto/caam/ |
D | Kconfig | 138 Supported cryptographic primitives: encryption, decryption,
|
/Linux-v5.4/Documentation/arm64/ |
D | pointer-authentication.rst | 16 The ARMv8.3 Pointer Authentication extension adds primitives that can be
|
/Linux-v5.4/Documentation/locking/ |
D | locktorture.rst | 9 that runs torture tests on core kernel locking primitives. The kernel
|
/Linux-v5.4/Documentation/livepatch/ |
D | callbacks.rst | 17 with memory barriers and kernel synchronization primitives, like
|
12