/openbmc/linux/Documentation/RCU/ |
H A D | checklist.rst | 28 read-side primitives is critically important. 91 primitives to add, remove, and replace elements on 108 appear atomic, as will individual atomic primitives. 111 of multiple atomic primitives. One alternative is to 156 various "_rcu()" list-traversal primitives, such 160 primitives. This is particularly useful in code that 167 list-traversal primitives can substitute for a good 171 and list_add_rcu() primitives must be used in order 228 primitives such as call_rcu(). 334 9. All RCU list-traversal primitives, which include [all …]
|
H A D | lockdep.rst | 14 In addition, RCU provides the following primitives that check lockdep's 30 checking of rcu_dereference() primitives: 107 traversal primitives check for being called from within an RCU read-side 110 traversal primitives will complain only if the lockdep expression is
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | ordering.txt | 46 Note well that many of these primitives generate absolutely no code 58 The Linux-kernel primitives that provide full ordering include: 65 o RCU's grace-period primitives. 113 Finally, RCU's grace-period primitives provide full ordering. These 114 primitives include synchronize_rcu(), synchronize_rcu_expedited(), 117 Furthermore, RCU's grace-period primitives can only be invoked in 118 sleepable contexts. Therefore, RCU's grace-period primitives are 378 Compared to locking primitives and RMW atomic operations, markers 460 primitives required the compiler to emit the corresponding store 468 primitives required the compiler to emit the corresponding load [all …]
|
H A D | simple.txt | 52 Please use the standard locking primitives provided by the kernel rather 53 than rolling your own. For one thing, the standard primitives interact 54 properly with lockdep. For another thing, these primitives have been 131 Packaged primitives: Sequence locking 148 primitives. (LKMM does not yet know about sequence locking, so it is 153 Packaged primitives: RCU 168 Packaged primitives: Atomic operations 194 Reading code using these primitives is often also quite helpful. 223 WRITE_ONCE() can safely be used in some cases. These primitives provide 226 One example use for these primitives is statistics, such as per-CPU [all …]
|
H A D | README | 15 like an overview of the types of low-level concurrency primitives 20 o You are familiar with the Linux-kernel concurrency primitives 66 primitives by category.
|
/openbmc/qemu/scripts/ |
H A D | u2f-setup-gen.py | 18 from cryptography.hazmat.primitives.asymmetric import ec 19 from cryptography.hazmat.primitives.serialization import Encoding, \
|
/openbmc/u-boot/doc/device-tree-bindings/mailbox/ |
H A 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
|
/openbmc/qemu/docs/spin/ |
H A D | win32-qemu-event.promela | 25 /* Basic sanity checking: test the Win32 event primitives */ 31 * primitives. SET/RESET/WAIT have exactly the same semantics as
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-posix-ipc_1.1.1.bb | 1 DESCRIPTION = "POSIX IPC primitives (semaphores, shared memory and message queues) for Python"
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/libsdl/ |
H A D | libsdl-gfx_2.0.25.bb | 1 SUMMARY = "SDL graphics drawing primitives and other support functions"
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python-pycryptodome.inc | 3 cryptographic primitives."
|
H A D | python3-cryptography_42.0.5.bb | 1 SUMMARY = "Provides cryptographic recipes and primitives to python developers"
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/zchunk/ |
H A D | zchunk_1.4.0.bb | 20 # Use OpenSSL primitives for SHA
|
/openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | nvidia,tegra186-hsp.yaml | 16 primitives for interprocessor communication. So the interprocessor 18 primitives, when operating between two processors not in an SMP
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/concurrencykit/ |
H A D | concurrencykit_git.bb | 1 DESCRIPTION = "Concurrency Kit provides a plethora of concurrency primitives, \
|
/openbmc/linux/tools/testing/selftests/powerpc/ |
H A D | Makefile | 26 primitives \
|
/openbmc/linux/Documentation/core-api/ |
H A D | genericirq.rst | 121 primitives referenced by the assigned chip descriptor structure. 183 The helper functions call the chip primitives and are used by the 279 The simple flow handler does not call any handler/chip primitives. 367 These primitives are strictly intended to mean what they say: ack means 386 chip primitives. The per-irq structure is protected via desc->lock, by
|
/openbmc/linux/Documentation/devicetree/bindings/firmware/ |
H A D | nvidia,tegra210-bpmp.txt | 16 - reg: physical base address and length for HW synchornization primitives
|
/openbmc/qemu/host/include/aarch64/host/ |
H A D | store-insert-al16.h.inc | 23 * GCC only implements __sync* primitives for int128 on aarch64.
|
/openbmc/linux/Documentation/driver-api/usb/ |
H A 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
|
/openbmc/linux/Documentation/locking/ |
H A D | locktypes.rst | 12 The kernel provides a variety of locking primitives which can be divided 34 versions of these primitives. In short, don't acquire sleeping locks from 59 preemption and interrupt disabling primitives. Contrary to other locking 165 interrupt disabling and enabling primitives: 177 primitives: 180 of the protection scope while the regular primitives are scopeless and
|
/openbmc/linux/include/linux/ |
H A D | intel_rapl.h | 85 u64 primitives[NR_RAPL_PRIMITIVES]; member
|
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-lib/ |
H A D | pixman_0.42.2.bb | 4 Porter/Duff model and implicit mask generation for geometric primitives \
|
/openbmc/qemu/docs/devel/ |
H A D | lockcnt.txt | 49 One may think of using the RCU primitives, rcu_read_lock() and 80 A QemuLockCnt comprises both a counter and a mutex; it has primitives 254 Again, the RCU primitives are used because new items can be added to the
|
/openbmc/u-boot/doc/ |
H A D | README.sched | 16 - There are NO primitives for thread synchronization (locking,
|