litmus-rt.git/kernel/time/Makefile, branch master

clockevents: Remove CONFIG_GENERIC_CLOCKEVENTS_BUILD

2015-04-01T12:22:57+00:00

This option was for simpler migration to the clock events code.
Most architectures have been converted and the option has been
disfunctional as a standalone option for quite some time. Remove
it.

Signed-off-by: Thomas Gleixner 
Signed-off-by: Rafael J. Wysocki 
Cc: Peter Zijlstra 
Link: http://lkml.kernel.org/r/5021859.jl9OC1medj@vostro.rjw.lan
Signed-off-by: Ingo Molnar

time: move the timecounter/cyclecounter code into its own file.

2014-12-30T23:29:25+00:00

The timecounter code has almost nothing to do with the clocksource
code. Let it live in its own file. This will help isolate the
timecounter users from the clocksource users in the source tree.

Signed-off-by: Richard Cochran 
Acked-by: Jeff Kirsher 
Signed-off-by: David S. Miller

time: Rename udelay_test.c to test_udelay.c

2014-11-21T19:59:55+00:00

Kees requested that this test module be renamed for consistency sake,
so this patch renames the udelay_test.c file (recently added to
tip/timers/core for 3.17) to test_udelay.c

Cc: Kees Cook 
Cc: Greg KH 
Cc: Stephen Rothwell 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: Linux-Next 
Cc: David Riley 
Signed-off-by: John Stultz

kernel: time: Add udelay_test module to validate udelay

2014-07-23T17:16:35+00:00

Create a module that allows udelay() to be executed to ensure that
it is delaying at least as long as requested (with a little bit of
error allowed).

There are some configurations which don't have reliably udelay
due to using a loop delay with cpufreq changes which should use
a counter time based delay instead.  This test aims to identify
those configurations where timing is unreliable.

Signed-off-by: David Riley 
Signed-off-by: John Stultz

time/timers: Move all time(r) related files into kernel/time

2014-06-23T09:22:35+00:00

Except for Kconfig.HZ. That needs a separate treatment.

Signed-off-by: Thomas Gleixner

tick: Fixup more fallout from hrtimer broadcast mode

2014-02-09T14:11:47+00:00

The hrtimer mode of broadcast is supported only when
GENERIC_CLOCKEVENTS_BROADCAST and TICK_ONESHOT config options
are enabled. Hence compile in the functions for hrtimer mode
of broadcast only when these options are selected.
Also fix max_delta_ticks value for the pseudo clock device.

Reported-by: Fengguang Wu 
Reported-by: Ingo Molnar 
Signed-off-by: Preeti U Murthy 
Link: http://lkml.kernel.org/r/52F719EE.9010304@linux.vnet.ibm.com
Signed-off-by: Thomas Gleixner

tick: Introduce hrtimer based broadcast

2014-02-07T14:34:29+00:00

On some architectures, in certain CPU deep idle states the local timers stop.
An external clock device is used to wakeup these CPUs. The kernel support for the
wakeup of these CPUs is provided by the tick broadcast framework by using the
external clock device as the wakeup source.

However not all implementations of architectures provide such an external
clock device. This patch includes support in the broadcast framework to handle
the wakeup of the CPUs in deep idle states on such systems by queuing a hrtimer
on one of the CPUs, which is meant to handle the wakeup of CPUs in deep idle states.

This patchset introduces a pseudo clock device which can be registered by the
archs as tick_broadcast_device in the absence of a real external clock
device. Once registered, the broadcast framework will work as is for these
architectures as long as the archs take care of the BROADCAST_ENTER
notification failing for one of the CPUs. This CPU is made the stand by CPU to
handle wakeup of the CPUs in deep idle and it *must not enter deep idle states*.

The CPU with the earliest wakeup is chosen to be this CPU. Hence this way the
stand by CPU dynamically moves around and so does the hrtimer which is queued
to trigger at the next earliest wakeup time. This is consistent with the case where
an external clock device is present. The smp affinity of this clock device is
set to the CPU with the earliest wakeup. This patchset handles the hotplug of
the stand by CPU as well by moving the hrtimer on to the CPU handling the CPU_DEAD
notification.

Originally-from: Thomas Gleixner 
Signed-off-by: Preeti U Murthy 
Cc: deepthi@linux.vnet.ibm.com
Cc: paulmck@linux.vnet.ibm.com
Cc: fweisbec@gmail.com
Cc: paulus@samba.org
Cc: srivatsa.bhat@linux.vnet.ibm.com
Cc: svaidy@linux.vnet.ibm.com
Cc: peterz@infradead.org
Cc: benh@kernel.crashing.org
Cc: rafael.j.wysocki@intel.com
Cc: linuxppc-dev@lists.ozlabs.org
Link: http://lkml.kernel.org/r/20140207080632.17187.80532.stgit@preeti.in.ibm.com
Signed-off-by: Thomas Gleixner

sched_clock: Make ARM's sched_clock generic for all architectures

2013-06-12T21:02:13+00:00

Nothing about the sched_clock implementation in the ARM port is
specific to the architecture. Generalize the code so that other
architectures can use it by selecting GENERIC_SCHED_CLOCK.

Signed-off-by: Stephen Boyd 
[jstultz: Merge minor collisions with other patches in my tree]
Signed-off-by: John Stultz

power: Add option to log time spent in suspend

2013-05-29T19:57:34+00:00

Below is a patch from android kernel that maintains a histogram of
suspend times. Please review and provide feedback.

Statistices on the time spent in suspend are kept in
/sys/kernel/debug/sleep_time.

Cc: Android Kernel Team 
Cc: Colin Cross 
Cc: Todd Poynor 
Cc: San Mehat 
Cc: Benoit Goby 
Cc: John Stultz 
Cc: Thomas Gleixner 
Signed-off-by: Colin Cross 
Signed-off-by: Todd Poynor 
[zoran.markovic@linaro.org: Re-formatted suspend time table to better
fit expected values. Moved accounting of suspend time into timekeeping
core. Removed CONFIG_SUSPEND_TIME flag and made the feature conditional
on CONFIG_DEBUG_FS. Changed the file name to sleep_time to better fit
terminology in timekeeping core. Changed seq_printf to seq_puts. Tweaked
commit message]
Signed-off-by: Zoran Markovic 
Signed-off-by: John Stultz

time: remove the timecompare code.

2012-11-01T15:41:35+00:00

This patch removes the timecompare code from the kernel. The top five
reasons to do this are:

1. There are no more users of this code.
2. The original idea was a bit weak.
3. The original author has disappeared.
4. The code was not general purpose but tuned to a particular hardware,
5. There are better ways to accomplish clock synchronization.

Signed-off-by: Richard Cochran 
Acked-by: John Stultz 
Tested-by: Bob Liu 
Signed-off-by: David S. Miller