linux-toradex.git/include/linux/hrtimer.h, branch Colibri_T30_LinuxImageV2.1Beta2_20140206

Fix some kernel-doc warnings

2011-06-27T23:06:19+00:00

Fix 'make htmldocs' warnings:

  Warning(/include/linux/hrtimer.h:153): No description found for parameter 'clockid'
  Warning(/include/linux/device.h:604): Excess struct/union/enum/typedef member 'of_match' description in 'device'
  Warning(/include/net/sock.h:349): Excess struct/union/enum/typedef member 'sk_rmem_alloc' description in 'sock'

Signed-off-by: Vitaliy Ivanov 
Acked-by: Grant Likely 
Acked-by: David S. Miller 
Signed-off-by: Linus Torvalds

hrtimers: Reorder clock bases

2011-05-23T11:59:54+00:00

The ordering of the clock bases is historical due to the
CLOCK_REALTIME and CLOCK_MONOTONIC constants. Now the hrtimer bases
have their own enumeration due to the gap between CLOCK_MONOTONIC and
CLOCK_BOOTTIME. So we can be more clever as most timers end up on the
CLOCK_MONOTONIC base due to the virtue of POSIX declaring that
relative CLOCK_REALTIME timers are not affected by time changes. In
desktop environments this is slowly changing as applications switch to
absolute timers, but I've observed empty CLOCK_REALTIME bases often
enough. There is no performance penalty or overhead when
CLOCK_REALTIME timers are active, but in case they are not we don't
skip over a full cache line.

Signed-off-by: Thomas Gleixner 
Reviewed-by: Peter Zijlstra

hrtimers: Avoid touching inactive timer bases

2011-05-23T11:59:54+00:00

Instead of iterating over all possible timer bases avoid it by marking
the active bases in the cpu base.

Signed-off-by: Thomas Gleixner 
Reviewed-by: Peter Zijlstra

hrtimers: Make struct hrtimer_cpu_base layout less stupid

2011-05-23T11:59:53+00:00

In the HIGHRES=y case we access the members at the end of struct
hrtimer_cpu_base first and then the one at the beginning. Move the
hrtimer data to front, so we have linear progressing access.

Signed-off-by: Thomas Gleixner 
Reviewed-by: Peter Zijlstra

timerfd: Manage cancelable timers in timerfd

2011-05-23T11:59:53+00:00

Peter is concerned about the extra scan of CLOCK_REALTIME_COS in the
timer interrupt. Yes, I did not think about it, because the solution
was so elegant. I didn't like the extra list in timerfd when it was
proposed some time ago, but with a rcu based list the list walk it's
less horrible than the original global lock, which was held over the
list iteration.

Requested-by: Peter Zijlstra 
Signed-off-by: Thomas Gleixner 
Reviewed-by: Peter Zijlstra

timerfd: Allow timers to be cancelled when clock was set

2011-05-02T19:39:15+00:00

Some applications must be aware of clock realtime being set
backward. A simple example is a clock applet which arms a timer for
the next minute display. If clock realtime is set backward then the
applet displays a stale time for the amount of time which the clock
was set backwards. Due to that applications poll the time because we
don't have an interface.

Extend the timerfd interface by adding a flag which puts the timer
onto a different internal realtime clock. All timers on this clock are
expired whenever the clock was set.

The timerfd core records the monotonic offset when the timer is
created. When the timer is armed, then the current offset is compared
to the previous recorded offset. When it has changed, then
timerfd_settime returns -ECANCELED. When a timer is read the offset is
compared and if it changed -ECANCELED returned to user space. Periodic
timers are not rearmed in the cancelation case.

Signed-off-by: Thomas Gleixner 
Acked-by: John Stultz 
Cc: Chris Friesen 
Tested-by: Kay Sievers 
Cc: "Kirill A. Shutemov" 
Cc: Peter Zijlstra 
Cc: Davide Libenzi 
Reviewed-by: Alexander Shishkin 
Link: http://lkml.kernel.org/r/%3Calpine.LFD.2.02.1104271359580.3323%40ionos%3E
Signed-off-by: Thomas Gleixner

hrtimers: Prepare for cancel on clock was set timers

2011-05-02T19:37:58+00:00

Make clock_was_set() unconditional and rename hres_timers_resume to
hrtimers_resume. This is a preparatory patch for hrtimers which are
cancelled when clock realtime was set.

Signed-off-by: Thomas Gleixner

hrtimer: Update hrtimer->state documentation

2011-03-10T18:15:58+00:00

We changed some of the state bits and combinations thereof over time,
but never updated the documentation.

Signed-off-by: Thomas Gleixner

timers: Add CLOCK_BOOTTIME hrtimer base

2011-02-21T20:53:08+00:00

CLOCK_MONOTONIC stops while the system is in suspend. This is because
to applications system suspend is invisible. However, there is a
growing set of applications that are wanting to be suspend-aware,
but do not want to deal with the complications of CLOCK_REALTIME
(which might jump around if settimeofday is called).

For these applications, I propose a new clockid: CLOCK_BOOTTIME.
CLOCK_BOOTTIME is idential to CLOCK_MONOTONIC, except it also
includes any time spent in suspend.

This patch add hrtimer base for CLOCK_BOOTTIME, using
get_monotonic_boottime/ktime_get_boottime, to allow
in kernel users to set timers against.

CC: Jamie Lokier 
CC: Thomas Gleixner 
CC: Alexander Shishkin 
CC: Arve Hjønnevåg 
Signed-off-by: John Stultz

time: Introduce get_monotonic_boottime and ktime_get_boottime

2011-02-21T20:53:05+00:00

This adds new functions that return the monotonic time since boot
(in other words, CLOCK_MONOTONIC + suspend time).

CC: Jamie Lokier 
CC: Thomas Gleixner 
CC: Alexander Shishkin 
CC: Arve Hjønnevåg 
Signed-off-by: John Stultz