Lines Matching +full:real +full:- +full:time

30 .Nd kernel time counters subsystem
32 The kernel uses several types of time-related devices, such as: real time clocks,
33 time counters and event timers.
34 Real time clocks are responsible for tracking real world time, mostly when the system
36 Time counters are responsible for tracking purposes, when the system is running.
37 Event timers are responsible for generating interrupts at a specified time or
38 periodically, to run different time-based events.
41 Time counters are the lowest level of time tracking in the kernel.
45 performance-critical places like the process scheduler.
47 More usable time is created by scaling the values read from the selected
48 time counter and combining it with some offset, regularly updated by
55 The goal of the time counters subsystem is to provide a unified way to access
58 Each driver implementing time counters registers them with the subsystem.
59 It is possible to see the list of present time counters, via the
63 .Bd -literal
64 kern.timecounter.choice: TSC-low(-100) HPET(950) i8254(0) ACPI-fast(900) dummy(-1000000)
65 kern.timecounter.tc.ACPI-fast.mask: 16777215
66 kern.timecounter.tc.ACPI-fast.counter: 13467909
67 kern.timecounter.tc.ACPI-fast.frequency: 3579545
68 kern.timecounter.tc.ACPI-fast.quality: 900
77 kern.timecounter.tc.TSC-low.mask: 4294967295
78 kern.timecounter.tc.TSC-low.counter: 4067509463
79 kern.timecounter.tc.TSC-low.frequency: 11458556
80 kern.timecounter.tc.TSC-low.quality: -100
84 .Bl -inset
92 is an integral value, defining the quality of this time counter
94 A negative value means this time counter is broken and should not be used.
97 The time management code of the kernel automatically switches to a
98 higher-quality time counter when it registers, unless the
102 There is no way to unregister a time counter once it has registered
104 If a dynamically loaded module contains a time counter you will not
105 be able to unload that module, even if the time counter it contains