Lines Matching refs:system
24 The purpose of the clock source is to provide a timeline for the system that
26 a Linux system will eventually read the clock source to determine exactly
31 It will ideally NEVER stop ticking as long as the system is running. It
32 may stop during system suspend.
47 the user-visible time to RTC clocks in the system or against networked time
49 the clock source, which provides the fundamental timeline for the system.
51 system to the shortcomings of it.
80 compensation code on both sides of the wrap point so that the system timeline
94 fire interrupts, so as to trigger events on the system timeline. On an SMP
95 system, it is ideal (and customary) to have one such event driving timer per
103 attribute however: the system will not try to plan events beyond the time
112 number of nanoseconds since the system was started. An architecture may or
114 implementation is not provided, the system jiffy counter will be used as
117 As the name suggests, sched_clock() is used for scheduling the system,
135 and will likely show up in system benchmarks.
137 The clock driving sched_clock() may stop or reset to zero during system
139 events on the system. However it may result in interesting timestamps in
154 drift between the CPUs on the system. The kernel can work around this by
167 Let's hope that your system is running on maximum frequency when this value