| /linux-5.10/kernel/sched/ |
| D | clock.c | 3 * sched_clock() for unstable CPU clocks
75 * We must start with !__sched_clock_stable because the unstable -> stable
76 * transition is accurate, while the stable -> unstable transition is not.
124 * Since we're still unstable and the tick is already running, we have in __set_sched_clock_stable()
130 * Attempt to make the (initial) unstable->stable transition continuous. in __set_sched_clock_stable()
152 * "tsc=unstable".
170 …printk(KERN_WARNING "TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unsta… in __sched_clock_work()
171 printk(KERN_INFO "sched_clock: Marking unstable (%lld, %lld)<-(%lld, %lld)\n", in __sched_clock_work()
224 * notably: acpi_processor and intel_idle, which can mark the TSC as unstable.
416 * TSC to be unstable, any computation will be computing crap. in sched_clock_tick_stable()
|
| /linux-5.10/mm/ |
| D | ksm.c | 64 * Therefore KSM uses two data structures - the stable and the unstable tree.
87 * unstable tree: this tree holds pointers to pages which have been found to
88 * be "unchanged for a period of time". The unstable tree sorts these pages
90 * upon the unstable tree to work correctly - the unstable tree is liable to
91 * be corrupted as its contents are modified, and so it is called unstable.
95 * 1) The unstable tree is flushed every time KSM completes scanning all
97 * 2) KSM will only insert into the unstable tree, pages whose hash value
99 * 3) The unstable tree is a RedBlack Tree - so its balancing is based on the
105 * take 10 attempts to find a page in the unstable tree, once it is found,
107 * compare it against the stable tree, and then against the unstable tree.)
[all …]
|
| /linux-5.10/include/linux/ |
| D | smp.h | 201 * raw_processor_id() - get the current (unstable) CPU id
203 * For then you know what you are doing and need an unstable
224 * Allow the architecture to differentiate between a stable and unstable read.
225 * For example, x86 uses an IRQ-safe asm-volatile read for the unstable but a
|
| /linux-5.10/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-5.10/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-5.10/arch/arm/boot/dts/ |
| 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-5.10/Documentation/ABI/obsolete/ |
| D | sysfs-class-net-mesh | 13 Contact: Antonio Quartulli <a@unstable.cc>
75 Contact: Antonio Quartulli <a@unstable.cc>
|
| D | sysfs-class-net-batman-adv | 27 Contact: Antonio Quartulli <a@unstable.cc>
|
| /linux-5.10/drivers/gpu/drm/i915/ |
| D | Kconfig | 145 menu "drm/i915 Unstable Evolution"
148 source "drivers/gpu/drm/i915/Kconfig.unstable"
|
| D | Kconfig.unstable | 3 bool "Enable unstable API for early prototype development"
|
| /linux-5.10/kernel/time/ |
| D | clocksource.c | 140 * watchdog_list will find the unstable clock again. in clocksource_watchdog_work()
168 * clocksource_mark_unstable - mark clocksource unstable via watchdog
169 * @cs: clocksource to be marked unstable
171 * This function is called by the x86 TSC code to mark clocksources as unstable;
202 /* Clocksource already marked unstable? */ in clocksource_watchdog()
239 …pr_warn("timekeeping watchdog on CPU%d: Marking clocksource '%s' as unstable because the skew is t… in clocksource_watchdog()
759 …pr_warn("Override clocksource %s is unstable and not HRT compatible - cannot switch while in HRT/N… in __clocksource_select()
820 * Run the watchdog first to eliminate unstable clock sources in clocksource_done_booting()
|
| /linux-5.10/drivers/mtd/ |
| D | sm_ftl.c | 336 if (ftl->unstable) in sm_write_sector()
380 if (ftl->unstable) in sm_write_block()
441 if (ftl->unstable) in sm_mark_block_bad()
470 if (ftl->unstable) in sm_erase_block()
735 if (!ftl->unstable) { in sm_recheck_media()
736 sm_printk("media unstable, not allowing writes"); in sm_recheck_media()
737 ftl->unstable = 1; in sm_recheck_media()
930 if (ftl->unstable) in sm_cache_flush()
950 if (ftl->unstable) in sm_cache_flush()
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ti/ |
| D | clockdomain.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | fapll.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | autoidle.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | adpll.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | fixed-factor-clock.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| D | composite.txt | 3 Binding status: Unstable - ABI compatibility may be broken in the future
|
| /linux-5.10/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-5.10/Documentation/devicetree/bindings/clock/ |
| D | keystone-gate.txt | 1 Status: Unstable - ABI compatibility may be broken in the future
|
| /linux-5.10/arch/x86/kernel/ |
| D | tsc.c | 41 * TSC can be unstable due to cpufreq or due to unsynced TSCs
229 * unstable. We do this because unlike Time Of Day, in native_sched_clock()
301 if (!strcmp(str, "unstable")) in tsc_setup()
972 * as unstable and give up in those cases.
1106 pr_info("Marking TSC unstable due to clocksource watchdog\n"); in tsc_cs_mark_unstable()
1172 pr_info("Marking TSC unstable due to %s\n", reason); in mark_tsc_unstable()
1219 * Exceptions must mark TSC as unstable: in unsynchronized_tsc()
1313 /* Don't bother refining TSC on unstable systems */ in tsc_refine_calibration_work()
|
| /linux-5.10/scripts/package/ |
| D | mkdebian | 130 distribution="unstable"
131 echo >&2 "Using default distribution of 'unstable' in the changelog"
|
| /linux-5.10/include/xen/interface/io/ |
| D | 9pfs.h | 32 * https://xenbits.xen.org/docs/unstable/misc/9pfs.html
|
| /linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-power-twl4030 | 17 This is useful for unstable power sources
|
| /linux-5.10/Documentation/devicetree/bindings/ |
| D | ABI.rst | 34 4) Don't submit bindings for staging or unstable. That will be decided by
|