| /linux-6.14.4/Documentation/core-api/ |
| 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 …]
|
| /linux-6.14.4/rust/kernel/alloc/ |
| D | allocator.rs | 52 // which together with the slab guarantees means the `krealloc` will return a properly aligned in aligned_size()
78 /// # Guarantees
80 /// This method has the same guarantees as `Allocator::realloc`. Additionally
109 // - Those functions provide the guarantees of this function. in call()
125 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that
128 // - `realloc` satisfies the guarantees, since `ReallocFunc::call` has the same.
142 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that
145 // - `realloc` satisfies the guarantees, since `ReallocFunc::call` has the same.
166 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that
169 // - `realloc` satisfies the guarantees, since `ReallocFunc::call` has the same.
|
| D | allocator_test.rs | 36 // - `realloc` provides the guarantees as provided in the `# Guarantees` section.
|
| /linux-6.14.4/Documentation/block/ |
| 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 a 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 …]
|
| /linux-6.14.4/rust/kernel/list/ |
| D | impl_list_item_mod.rs | 127 // SAFETY: See GUARANTEES comment on each method.
129 // GUARANTEES:
135 // SAFETY: The caller guarantees that `me` points at a valid value of type `Self`.
141 // GUARANTEES:
158 // GUARANTEES:
171 // GUARANTEES:
191 // SAFETY: See GUARANTEES comment on each method.
193 // GUARANTEES:
224 // GUARANTEES:
238 // GUARANTEES: (always)
[all …]
|
| /linux-6.14.4/rust/kernel/ |
| D | alloc.rs | 137 /// - Implementers must ensure that all trait functions abide by the guarantees documented in the
138 /// `# Guarantees` sections.
147 /// # Guarantees
167 /// to `realloc` guarantees that the new or grown buffer has at least `Layout::size` bytes, but
186 /// # Guarantees
188 /// This function has the same guarantees as [`Allocator::alloc`]. When `ptr == Some(p)`, then
189 /// it additionally guarantees that:
211 // SAFETY: The caller guarantees that `ptr` points at a valid allocation created by this in free()
|
| D | page.rs | 176 // it has performed a bounds check and guarantees that `src` is in read_raw()
179 // There caller guarantees that there is no data race. in read_raw()
198 // bounds check and guarantees that `dst` is valid for `len` bytes. in write_raw()
200 // There caller guarantees that there is no data race. in write_raw()
218 // bounds check and guarantees that `dst` is valid for `len` bytes. in fill_zero_raw()
220 // There caller guarantees that there is no data race. in fill_zero_raw()
246 // bounds check and guarantees that `dst` is valid for `len` bytes. Furthermore, we have in copy_from_user_slice_raw()
247 // exclusive access to the slice since the caller guarantees that there are no races. in copy_from_user_slice_raw()
|
| D | driver.rs | 76 // SAFETY: `try_ffi_init` guarantees that `ptr` is valid for write. in new()
79 // SAFETY: `try_ffi_init` guarantees that `ptr` is valid for write, and it has in new()
93 // SAFETY: The existence of `self` guarantees that `self.reg` has previously been in drop()
|
| D | firmware.rs | 69 // SAFETY: `func` not bailing out with a non-zero error code, guarantees that `fw` is a in request_internal()
98 // `bindings::firmware` guarantees, if successfully requested, that in data()
|
| D | list.rs | 64 /// Implementers must ensure that they provide the guarantees documented on methods provided by
71 /// # Guarantees
88 /// # Guarantees
104 /// # Guarantees
122 /// # Guarantees
384 // SAFETY: We just checked that `item` is in a list, so the caller guarantees that it in remove()
456 // SAFETY: The above call to `post_remove` guarantees that we can recreate the `ListArc`. in remove_internal_inner()
|
| /linux-6.14.4/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-numa | 22 the guarantees of cpusets. This should not be enabled
24 guarantees.
|
| /linux-6.14.4/arch/s390/include/asm/ |
| D | kmsan.h | 46 * Note, this sacrifices occasionally breaking scheduling guarantees. in kmsan_virt_addr_valid()
48 * performance guarantees due to being heavily instrumented. in kmsan_virt_addr_valid()
|
| /linux-6.14.4/arch/parisc/include/asm/ |
| 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
|
| /linux-6.14.4/tools/memory-model/Documentation/ |
| 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
|
| /linux-6.14.4/arch/x86/include/asm/ |
| 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()
|
| /linux-6.14.4/arch/riscv/include/asm/ |
| D | bitops.h | 266 * Note: there are no guarantees that this function will not be reordered
268 * make sure not to rely on its reordering guarantees.
283 * Note: there are no guarantees that this function will not be reordered
285 * make sure not to rely on its reordering guarantees.
|
| /linux-6.14.4/arch/arm/nwfpe/ |
| 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
|
| /linux-6.14.4/kernel/livepatch/ |
| 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
|
| /linux-6.14.4/drivers/gpu/drm/i915/gem/ |
| 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()
|
| /linux-6.14.4/kernel/ |
| D | Kconfig.preempt | 28 time, but there are no guarantees and occasional longer delays
104 require real-time guarantees.
|
| /linux-6.14.4/lib/ |
| D | Kconfig.kgdb | 141 'go', KDB tries to continue. No guarantees that the
144 No guarantees that the kernel is still usable in this situation.
|
| /linux-6.14.4/include/linux/ |
| D | dm-bufio.h | 107 * dm_bufio_write_dirty_buffers guarantees that the buffer is on-disk but
127 * Write all dirty buffers. Guarantees that all dirty buffers created prior
|
| /linux-6.14.4/drivers/mmc/core/ |
| D | sd_ops.c | 318 /* NOTE: caller guarantees scr is heap-allocated */ in mmc_app_send_scr()
368 /* NOTE: caller guarantees resp is heap-allocated */ in mmc_sd_switch()
388 /* NOTE: caller guarantees ssr is heap-allocated */ in mmc_app_sd_status()
|
| /linux-6.14.4/rust/kernel/fs/ |
| D | file.rs | 275 // SAFETY: The caller guarantees that the pointer is not dangling and stays valid for the in from_raw_file()
278 // INVARIANT: The caller guarantees that there are no problematic `fdget_pos` calls. in from_raw_file()
331 // SAFETY: The file is valid because the shared reference guarantees a nonzero refcount. in flags()
349 // SAFETY: The caller guarantees that the pointer is not dangling and stays valid for the in from_raw_file()
352 // INVARIANT: The caller guarantees that there are no problematic `fdget_pos` calls. in from_raw_file()
|
| /linux-6.14.4/tools/testing/selftests/arm64/pauth/ |
| D | pac_corruptor.S | 9 * also guarantees no possible collision. TCR_EL1.TBI0 is set by default so no
|