hrtimer: Provide clock_was_set_delayed()
authorJohn Stultz <johnstul@us.ibm.com>
Tue, 10 Jul 2012 22:43:19 +0000 (18:43 -0400)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 25 Jul 2012 03:11:34 +0000 (04:11 +0100)
commit3c910e7e46810c73e21196867b7ec63d58a0a45c
treef2ff5b38a63d10840342af09126c8f13db05394f
parentb19f4db486601885ee4c40665f4e8509ec65b4d5
hrtimer: Provide clock_was_set_delayed()

commit f55a6faa384304c89cfef162768e88374d3312cb upstream.

clock_was_set() cannot be called from hard interrupt context because
it calls on_each_cpu().

For fixing the widely reported leap seconds issue it is necessary to
call it from hard interrupt context, i.e. the timer tick code, which
does the timekeeping updates.

Provide a new function which denotes it in the hrtimer cpu base
structure of the cpu on which it is called and raise the hrtimer
softirq. We then execute the clock_was_set() notificiation from
softirq context in run_hrtimer_softirq(). The hrtimer softirq is
rarely used, so polling the flag there is not a performance issue.

[ tglx: Made it depend on CONFIG_HIGH_RES_TIMERS. We really should get
  rid of all this ifdeffery ASAP ]

Signed-off-by: John Stultz <johnstul@us.ibm.com>
Reported-by: Jan Engelhardt <jengelh@inai.de>
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Prarit Bhargava <prarit@redhat.com>
Link: http://lkml.kernel.org/r/1341960205-56738-2-git-send-email-johnstul@us.ibm.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
include/linux/hrtimer.h
kernel/hrtimer.c