Home
last modified time | relevance | path

Searched full:unstable (Results 1 – 25 of 221) sorted by relevance

123456789

/linux-6.12.1/Documentation/mm/damon/
Dmaintainer-profile.rst10 linux-mm@kvack.org. Patches should be made against the `mm-unstable tree
11 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ whenever possible and posted
20 Sufficiently reviewed patches will be queued in `mm-unstable
21 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ by the memory management
26 Note again the patches for `mm-unstable tree
27 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ are queued by the memory
30 in mm-unstable, please make sure the requirement is clearly specified.
56 Patches can be sent anytime. Key cycle dates of the `mm-unstable
57 <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and `mm-stable
/linux-6.12.1/kernel/sched/
Dclock.c3 * 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.12.1/Documentation/process/
Dprogramming-language.rst42 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.12.1/mm/
Dksm.c73 * 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.12.1/include/linux/
Dsmp.h237 * raw_processor_id() - get the current (unstable) CPU id
239 * For then you know what you are doing and need an unstable
260 * Allow the architecture to differentiate between a stable and unstable read.
261 * For example, x86 uses an IRQ-safe asm-volatile read for the unstable but a
/linux-6.12.1/tools/testing/selftests/proc/
Dproc-2-is-kthread.c34 * kthread creation API is formally unstable internal kernel API, in main()
38 * but their PIDs are unstable. in main()
/linux-6.12.1/net/netfilter/
Dnf_nat_bpf.c2 /* Unstable NAT Helpers for XDP and TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
Dnf_flow_table_bpf.c2 /* Unstable Flow Table Helpers for XDP hook
7 * unstable.
/linux-6.12.1/net/xfrm/
Dxfrm_interface_bpf.c2 /* Unstable XFRM Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
Dxfrm_state_bpf.c2 /* Unstable XFRM state BPF helpers.
5 * interface they are exposed through to BPF programs is explicitly unstable.
/linux-6.12.1/net/ipv4/
Dfou_bpf.c2 /* Unstable Fou Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dvidioc-query-dv-timings.rst58 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.12.1/arch/arm/boot/dts/nxp/imx/
Dimx6q-cm-fx6.dts181 * the module behaves unstable at this frequency. Hence, remove the
203 * the module behaves unstable at this frequency. Hence, remove the
225 * the module behaves unstable at this frequency. Hence, remove the
247 * the module behaves unstable at this frequency. Hence, remove the
/linux-6.12.1/Documentation/scheduler/
Dsched-rt-group.rst21 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.12.1/Documentation/translations/it_IT/process/
Dprogramming-language.rst52 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.12.1/drivers/mtd/
Dsm_ftl.c337 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.12.1/Documentation/maintainer/
Drebasing-and-merging.rst57 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.12.1/
D.rustfmt.toml4 # Unstable options that help catching some mistakes in formatting and that we may want to enable
/linux-6.12.1/include/xen/interface/io/
D9pfs.h15 * https://xenbits.xen.org/docs/unstable/misc/9pfs.html
/linux-6.12.1/drivers/md/dm-vdo/indexer/
Dradix-sort.h10 * Radix sort is implemented using an American Flag sort, an unstable, in-place 8-bit radix
/linux-6.12.1/kernel/time/
Dclocksource.c189 * watchdog_list will find the unstable clock again. in clocksource_watchdog_work()
217 * clocksource_mark_unstable - mark clocksource unstable via watchdog
218 * @cs: clocksource to be marked unstable
220 * This function is called by the x86 TSC code to mark clocksources as unstable;
284 …f %lldns vs. limit of %ldns, wd-wd read-back delay only %lldns, attempt %d, marking %s unstable\n", in cs_watchdog_read()
437 /* Clocksource already marked unstable? */ in clocksource_watchdog()
517 …pr_warn("timekeeping watchdog on CPU%d: Marking clocksource '%s' as unstable because the skew is t… in clocksource_watchdog()
1039 …pr_warn("Override clocksource %s is unstable and not HRT compatible - cannot switch while in HRT/N… in __clocksource_select()
1094 * Run the watchdog first to eliminate unstable clock sources in clocksource_done_booting()
/linux-6.12.1/arch/x86/kernel/
Dtsc.c43 * TSC can be unstable due to cpufreq or due to unsynced TSCs
244 * unstable. We do this because unlike Time Of Day, in native_sched_clock()
325 if (!strcmp(str, "unstable")) in tsc_setup()
1009 * as unstable and give up in those cases.
1144 pr_info("Marking TSC unstable due to clocksource watchdog\n"); in tsc_cs_mark_unstable()
1214 pr_info("Marking TSC unstable due to %s\n", reason); in mark_tsc_unstable()
1287 * Exceptions must mark TSC as unstable: in unsynchronized_tsc()
1322 /* Don't bother refining TSC on unstable systems */ in tsc_refine_calibration_work()
/linux-6.12.1/rust/
Dbindgen_parameters25 # nor Rust currently understand, and which Clang currently declares to be unstable.
/linux-6.12.1/scripts/package/
Dmkdebian175 distribution="unstable"
176 echo >&2 "Using default distribution of 'unstable' in the changelog"
/linux-6.12.1/Documentation/devicetree/bindings/pci/
Dpci-ep.yaml48 Endpoint Controller, otherwise an unstable (across boots) unique number

123456789