| /openbmc/linux/Documentation/core-api/ |
| H A D | refcount-vs-atomic.rst | 14 ``atomic_*()`` functions with regards to the memory ordering guarantees.
17 these memory ordering guarantees.
33 In the absence of any memory ordering guarantees (i.e. fully unordered)
35 program order (po) relation (on the same CPU). It guarantees that
41 A strong (full) memory ordering guarantees that all prior loads and
44 It also guarantees that all po-earlier stores on the same CPU
49 A RELEASE memory ordering guarantees that all prior loads and
51 before the operation. It also guarantees that all po-earlier
57 An ACQUIRE memory ordering guarantees that all post loads and
59 completed after the acquire operation. It also guarantees that all
[all …]
|
| /openbmc/linux/Documentation/block/ |
| H A D | bfq-iosched.rst | 9 - BFQ guarantees a high system and application responsiveness, and a
70 4-1 Service guarantees provided
84 Regardless of the actual background workload, BFQ guarantees that, for
126 Strong fairness, bandwidth and delay guarantees
132 guarantees, it is possible to compute tight per-I/O-request delay
133 guarantees by a simple formula. If not configured for strict service
134 guarantees, BFQ switches to time-based resource sharing (only) for
142 possibly heavy workloads are being served, BFQ guarantees:
193 - With respect to idling for service guarantees, if several
196 guarantees the expected throughput distribution without ever
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-numa | 22 the guarantees of cpusets. This should not be enabled
24 guarantees.
|
| /openbmc/linux/arch/riscv/include/asm/ |
| H A D | bitops.h | 106 * Note: there are no guarantees that this function will not be reordered
108 * make sure not to rely on its reordering guarantees.
123 * Note: there are no guarantees that this function will not be reordered
125 * make sure not to rely on its reordering guarantees.
|
| /openbmc/u-boot/arch/nios2/include/asm/bitops/ |
| H A D | atomic.h | 56 * if you do not require the atomic guarantees.
58 * Note: there are no guarantees that this function will not be reordered
60 * make sure not to rely on its reordering guarantees.
|
| /openbmc/linux/arch/parisc/include/asm/ |
| H A D | ldcw.h | 5 /* Because kmalloc only guarantees 8-byte alignment for kmalloc'd data,
6 and GCC only guarantees 8-byte alignment for stack locals, we can't
|
| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | locking.txt | 43 The basic rule guarantees that if CPU0() acquires mylock before CPU1(),
75 This converse to the basic rule guarantees that if CPU0() acquires
135 The smp_load_acquire() guarantees that its load from "flags" will
137 problem. The smp_store_release() guarantees that its store will be
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | kmsan.h | 89 * Note, this sacrifices occasionally breaking scheduling guarantees. in kmsan_virt_addr_valid()
91 * performance guarantees due to being heavily instrumented. in kmsan_virt_addr_valid()
|
| /openbmc/qemu/docs/devel/ |
| H A D | atomics.rst | 52 architectures, CPU guarantees are strong enough that blocking compiler
116 The only guarantees that you can rely upon in this case are:
143 - ``qatomic_load_acquire()``, which guarantees the LOAD to appear to
149 - ``qatomic_store_release()``, which guarantees the STORE to appear to
162 - ``smp_rmb()`` guarantees that all the LOAD operations specified before
170 - ``smp_wmb()`` guarantees that all the STORE operations specified before
178 - ``smp_mb_acquire()`` guarantees that all the LOAD operations specified before
183 - ``smp_mb_release()`` guarantees that all the STORE operations specified *after*
188 - ``smp_mb()`` guarantees that all the LOAD and STORE operations specified
|
| /openbmc/openbmc/poky/bitbake/lib/bb/ |
| H A D | daemonize.py | 33 # the command-line or shell. It also guarantees that the child will not
52 # based systems). This second fork guarantees that the child is no
|
| /openbmc/linux/kernel/ |
| H A D | Kconfig.preempt | 24 time, but there are no guarantees and occasional longer delays
85 require real-time guarantees.
|
| /openbmc/linux/arch/arm/nwfpe/ |
| H A D | ChangeLog | 61 comment in the code beside init_flag state the kernel guarantees
64 I couldn't even find anything that guarantees it is zeroed when
|
| /openbmc/linux/kernel/livepatch/ |
| H A D | shadow.c | 189 * This function guarantees that the constructor function is called only when
218 * This function guarantees that only one shadow variable exists with the given
219 * @id for the given @obj. It also guarantees that the constructor function
|
| /openbmc/linux/drivers/gpu/drm/i915/gem/ |
| H A D | i915_gem_busy.c | 26 * The uABI guarantees an active writer is also amongst the read in __busy_write_id()
47 * guarantees forward progress. We could rely on the idle worker in __busy_set_if_active()
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.kgdb | 140 'go', KDB tries to continue. No guarantees that the
143 No guarantees that the kernel is still usable in this situation.
|
| /openbmc/linux/drivers/mmc/core/ |
| H A D | sd_ops.c | 265 /* NOTE: caller guarantees scr is heap-allocated */ in mmc_app_send_scr()
315 /* NOTE: caller guarantees resp is heap-allocated */ in mmc_sd_switch()
336 /* NOTE: caller guarantees ssr is heap-allocated */ in mmc_app_sd_status()
|
| /openbmc/linux/include/linux/ |
| H A D | dm-bufio.h | 100 * dm_bufio_write_dirty_buffers guarantees that the buffer is on-disk but
120 * Write all dirty buffers. Guarantees that all dirty buffers created prior
|
| /openbmc/linux/tools/testing/selftests/arm64/pauth/ |
| H A D | pac_corruptor.S | 9 * also guarantees no possible collision. TCR_EL1.TBI0 is set by default so no
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Barr | 1 …ceiving a free copy for my personal examination and use. There are no guarantees that this packa…
|
| H A D | CrystalStacker | 5 NewCreature Design makes no guarantees regarding the Crystal Stacker software. We are not responsib…
|
| /openbmc/linux/net/dcb/ |
| H A D | Kconfig | 18 framework for assigning bandwidth guarantees to traffic classes.
|
| /openbmc/linux/drivers/greybus/ |
| H A D | hd.c | 71 /* Locking: Caller guarantees serialisation */
95 /* Locking: Caller guarantees serialisation */
|
| /openbmc/linux/net/sunrpc/xprtrdma/ |
| H A D | frwr_ops.c | 260 * largest r/wsize NFS will ask for. This guarantees that in frwr_query_device()
492 * memory regions. This guarantees that registered MRs are properly fenced
533 /* Strong send queue ordering guarantees that when the in frwr_unmap_sync()
598 * This guarantees that registered MRs are properly fenced from the
634 /* Strong send queue ordering guarantees that when the in frwr_unmap_async()
|
| /openbmc/linux/Documentation/ |
| H A D | memory-barriers.txt | 49 - Guarantees.
224 GUARANTEES
227 There are some minimal guarantees that may be expected of a CPU:
310 And there are anti-guarantees:
312 (*) These guarantees do not apply to bitfields, because compilers often
323 (*) These guarantees apply only to properly aligned and sized scalar
330 guarantees were introduced into the C11 standard, so beware when
414 the CPU under consideration guarantees that for any load preceding it,
472 This acts as a one-way permeable barrier. It guarantees that all memory
487 This also acts as a one-way permeable barrier. It guarantees that all
[all …]
|
| /openbmc/linux/block/ |
| H A D | Kconfig.iosched | 26 also guarantees a low latency to interactive and soft
|