Home
last modified time | relevance | path

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

12345678

/linux/Documentation/mm/damon/
H A 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/kernel/sched/
H A 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/Documentation/process/
H A 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/rust/pin-init/
H A DREADME.md32 This library requires the [`allocator_api` unstable feature] when the `alloc` feature is
36 [`allocator_api` unstable feature]: https://doc.rust-lang.org/nightly/unstable-book/library-feature…
45 This feature enables the `Wrapper` implementation on the unstable `core::pin::UnsafePinned` type.
46 This requires the [`unsafe_pinned` unstable feature](https://github.com/rust-lang/rust/issues/12573…
/linux/include/linux/
H A 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/tools/testing/selftests/proc/
H A 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/net/netfilter/
H A Dnf_nat_bpf.c2 /* Unstable NAT Helpers for XDP and TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
H A Dnf_flow_table_bpf.c2 /* Unstable Flow Table Helpers for XDP hook
7 * unstable.
/linux/net/xfrm/
H A Dxfrm_interface_bpf.c2 /* Unstable XFRM Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
H A Dxfrm_state_bpf.c2 /* Unstable XFRM state BPF helpers.
5 * interface they are exposed through to BPF programs is explicitly unstable.
/linux/net/ipv4/
H A Dfou_bpf.c2 /* Unstable Fou Helpers for TC-BPF hook
6 * are exposed through to BPF programs is explicitly unstable.
/linux/Documentation/userspace-api/media/v4l/
H A 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/arch/arm/boot/dts/nxp/imx/
H A 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/Documentation/scheduler/
H A 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/Documentation/translations/it_IT/process/
H A 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/drivers/mtd/
H A 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/Documentation/maintainer/
H A 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/drivers/gpu/drm/xe/
H A Dxe_device_sysfs.c76 * to PCIe Gen4 speed when faced with unstable link at Gen5, which makes
99 * auto-downgraded its link to PCIe Gen4 speed due to unstable Gen5 link.
/linux/
H A D.rustfmt.toml4 # Unstable options that help catching some mistakes in formatting and that we may want to enable
/linux/kernel/time/
H A Dclocksource.c190 * watchdog_list will find the unstable clock again. in clocksource_watchdog_work()
225 * clocksource_mark_unstable - mark clocksource unstable via watchdog
226 * @cs: clocksource to be marked unstable
228 * This function is called by the x86 TSC code to mark clocksources as unstable;
292 …f %lldns vs. limit of %ldns, wd-wd read-back delay only %lldns, attempt %d, marking %s unstable\n", in cs_watchdog_read()
448 /* Clocksource already marked unstable? */ in clocksource_watchdog()
528 …pr_warn("timekeeping watchdog on CPU%d: Marking clocksource '%s' as unstable because the skew is t… in clocksource_watchdog()
1059 …pr_warn("Override clocksource %s is unstable and not HRT compatible - cannot switch while in HRT/N… in __clocksource_select()
1114 * Run the watchdog first to eliminate unstable clock sources in clocksource_done_booting()
/linux/include/xen/interface/io/
H A D9pfs.h15 * https://xenbits.xen.org/docs/unstable/misc/9pfs.html
/linux/drivers/md/dm-vdo/indexer/
H A Dradix-sort.h10 * Radix sort is implemented using an American Flag sort, an unstable, in-place 8-bit radix
/linux/rust/kernel/
H A Ddevice_id.rs25 /// transmute; however, const trait functions relies on `const_trait_impl` unstable feature,
100 // SAFETY: this is effectively `array_assume_init`, which is unstable, so we use
/linux/scripts/package/
H A Dmkdebian185 distribution="unstable"
186 echo >&2 "Using default distribution of 'unstable' in the changelog"
/linux/Documentation/ABI/testing/
H A Dsysfs-class-power-twl403017 This is useful for unstable power sources

12345678