| /linux-6.8/Documentation/mm/damon/ |
| D | maintainer-profile.rst | 10 linux-mm@kvack.org. Patches should be made against the mm-unstable tree [1]_
18 Sufficiently reviewed patches will be queued in mm-unstable [1]_ by the memory
23 Note again the patches for review should be made against the mm-unstable
44 Patches can be sent anytime. Key cycle dates of the mm-unstable[1] and
56 .. [1] https://git.kernel.org/akpm/mm/h/mm-unstable
|
| /linux-6.8/kernel/sched/ |
| D | clock.c | 3 * sched_clock() for unstable CPU clocks
73 * We must start with !__sched_clock_stable because the unstable -> stable
74 * transition is accurate, while the stable -> unstable transition is not.
122 * Since we're still unstable and the tick is already running, we have in __set_sched_clock_stable()
128 * Attempt to make the (initial) unstable->stable transition continuous. in __set_sched_clock_stable()
150 * "tsc=unstable".
168 …printk(KERN_WARNING "TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unsta… in __sched_clock_work()
169 printk(KERN_INFO "sched_clock: Marking unstable (%lld, %lld)<-(%lld, %lld)\n", in __sched_clock_work()
222 * notably: acpi_processor and intel_idle, which can mark the TSC as unstable.
439 * TSC to be unstable, any computation will be computing crap. in sched_clock_tick_stable()
|
| /linux-6.8/rust/alloc/vec/ |
| D | extract_if.rs | 22 #[unstable(feature = "extract_if", reason = "recently added", issue = "43244")]
29 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global,
49 #[unstable(feature = "allocator_api", issue = "32838")]
56 #[unstable(feature = "extract_if", reason = "recently added", issue = "43244")]
92 #[unstable(feature = "extract_if", reason = "recently added", issue = "43244")]
|
| D | into_iter.rs | 37 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global,
94 #[unstable(feature = "allocator_api", issue = "32838")]
344 #[unstable(feature = "trusted_len", issue = "37572")]
366 #[unstable(issue = "none", feature = "std_internals")]
372 #[unstable(issue = "none", feature = "std_internals")]
376 #[unstable(issue = "none", feature = "std_internals")]
426 #[unstable(issue = "none", feature = "inplace_iteration")]
430 #[unstable(issue = "none", feature = "inplace_iteration")]
|
| D | drain.rs | 27 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator + 'a = Global,
64 #[unstable(feature = "allocator_api", issue = "32838")]
90 #[unstable(feature = "drain_keep_rest", issue = "101122")]
251 #[unstable(feature = "trusted_len", issue = "37572")]
|
| /linux-6.8/rust/alloc/collections/ |
| D | mod.rs | 71 #[unstable(
83 #[unstable(
99 #[unstable(
111 #[unstable(
123 #[unstable(feature = "try_reserve_kind", reason = "new API", issue = "48043")]
|
| /linux-6.8/Documentation/process/ |
| D | programming-language.rst | 42 On top of that, some unstable features [rust-unstable-features]_ are used in
43 the kernel. Unstable features may change in the future, thus it is an important
58 .. [rust-unstable-features] https://github.com/Rust-for-Linux/linux/issues/2
|
| /linux-6.8/rust/alloc/ |
| D | slice.rs | 38 #[unstable(feature = "slice_range", issue = "76393")]
40 #[unstable(feature = "array_chunks", issue = "74985")]
42 #[unstable(feature = "array_chunks", issue = "74985")]
44 #[unstable(feature = "array_windows", issue = "75027")]
52 #[unstable(feature = "slice_from_ptr_range", issue = "89792")]
62 #[unstable(feature = "slice_group_by", issue = "80552")]
183 /// When applicable, unstable sorting is preferred because it is generally faster than stable
236 /// When applicable, unstable sorting is preferred because it is generally faster than stable
281 /// When applicable, unstable sorting is preferred because it is generally faster than stable
437 #[unstable(feature = "allocator_api", issue = "32838")]
[all …]
|
| D | boxed.rs | 184 #[unstable(feature = "thin_box", issue = "92791")]
201 #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global,
243 #[unstable(feature = "new_uninit", issue = "63291")]
270 #[unstable(feature = "new_uninit", issue = "63291")]
304 #[unstable(feature = "allocator_api", issue = "32838")]
330 #[unstable(feature = "allocator_api", issue = "32838")]
331 // #[unstable(feature = "new_uninit", issue = "63291")]
356 #[unstable(feature = "allocator_api", issue = "32838")]
357 // #[unstable(feature = "new_uninit", issue = "63291")]
379 #[unstable(feature = "allocator_api", issue = "32838")]
[all …]
|
| /linux-6.8/mm/ |
| D | ksm.c | 73 * Therefore KSM uses two data structures - the stable and the unstable tree.
96 * unstable tree: this tree holds pointers to pages which have been found to
97 * be "unchanged for a period of time". The unstable tree sorts these pages
99 * upon the unstable tree to work correctly - the unstable tree is liable to
100 * be corrupted as its contents are modified, and so it is called unstable.
104 * 1) The unstable tree is flushed every time KSM completes scanning all
106 * 2) KSM will only insert into the unstable tree, pages whose hash value
108 * 3) The unstable tree is a RedBlack Tree - so its balancing is based on the
114 * take 10 attempts to find a page in the unstable tree, once it is found,
116 * compare it against the stable tree, and then against the unstable tree.)
[all …]
|
| /linux-6.8/include/linux/ |
| D | smp.h | 236 * raw_processor_id() - get the current (unstable) CPU id
238 * For then you know what you are doing and need an unstable
259 * Allow the architecture to differentiate between a stable and unstable read.
260 * For example, x86 uses an IRQ-safe asm-volatile read for the unstable but a
|
| /linux-6.8/net/netfilter/ |
| D | nf_nat_bpf.c | 2 /* Unstable NAT Helpers for XDP and TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
|
| /linux-6.8/net/xfrm/ |
| D | xfrm_interface_bpf.c | 2 /* Unstable XFRM Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
|
| D | xfrm_state_bpf.c | 2 /* Unstable XFRM state BPF helpers.
5 * interface they are exposed through to BPF programs is explicitly unstable.
|
| /linux-6.8/Documentation/userspace-api/media/v4l/ |
| D | vidioc-query-dv-timings.rst | 58 ENOLINK is returned. If a signal was detected, but it was unstable and
82 The signal was unstable and the hardware could not lock on to it.
|
| /linux-6.8/net/ipv4/ |
| D | fou_bpf.c | 2 /* Unstable Fou Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
|
| /linux-6.8/arch/arm/boot/dts/nxp/imx/ |
| D | imx6q-cm-fx6.dts | 172 * the module behaves unstable at this frequency. Hence, remove the
194 * the module behaves unstable at this frequency. Hence, remove the
216 * the module behaves unstable at this frequency. Hence, remove the
238 * the module behaves unstable at this frequency. Hence, remove the
|
| /linux-6.8/Documentation/scheduler/ |
| D | sched-rt-group.rst | 21 Fiddling with these settings can result in an unstable system, the knobs are
26 * very small values in sched_rt_period_us can result in an unstable
30 * very small values in sched_rt_runtime_us can result in an unstable
|
| /linux-6.8/Documentation/translations/it_IT/process/ |
| D | programming-language.rst | 52 instabili [it-rust-unstable-features]_. Queste funzionalità potrebbero cambiare
68 .. [it-rust-unstable-features] https://github.com/Rust-for-Linux/linux/issues/2
|
| /linux-6.8/drivers/mtd/ |
| D | sm_ftl.c | 337 if (ftl->unstable) in sm_write_sector()
382 if (ftl->unstable) in sm_write_block()
444 if (ftl->unstable) in sm_mark_block_bad()
474 if (ftl->unstable) in sm_erase_block()
742 if (!ftl->unstable) { in sm_recheck_media()
743 sm_printk("media unstable, not allowing writes"); in sm_recheck_media()
744 ftl->unstable = 1; in sm_recheck_media()
942 if (ftl->unstable) in sm_cache_flush()
962 if (ftl->unstable) in sm_cache_flush()
|
| /linux-6.8/drivers/gpu/drm/ci/xfails/ |
| D | rockchip-rk3399-skips.txt | 4 # Too unstable, machine ends up hanging after lots of Oopses
|
| /linux-6.8/Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 57 expose an unstable branch for others to test with or for automated
58 testing services. If you do expose a branch that may be unstable in
72 as the new base. The kernel is often in a relatively unstable state
|
| /linux-6.8/ |
| D | .rustfmt.toml | 4 # Unstable options that help catching some mistakes in formatting and that we may want to enable
|
| /linux-6.8/include/xen/interface/io/ |
| D | 9pfs.h | 15 * https://xenbits.xen.org/docs/unstable/misc/9pfs.html
|
| /linux-6.8/Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|