linux-stable.git/kernel/time/tick-internal.h, branch v4.1.2

clockevents: Cleanup dead cpu explicitely

2015-04-03T06:44:37+00:00

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call. We are way better off to have explicit
calls instead of this monstrosity.

Split out the cleanup function for a dead cpu and invoke it
directly from the cpu down code. Make it conditional on
CPU_HOTPLUG as well.

Temporary change, will be refined in the future.

Signed-off-by: Thomas Gleixner 
[ Rebased, added clockevents_notify() removal ]
Signed-off-by: Rafael J. Wysocki 
Cc: Peter Zijlstra 
Link: http://lkml.kernel.org/r/1735025.raBZdQHM3m@vostro.rjw.lan
Signed-off-by: Ingo Molnar

clockevents: Make tick handover explicit

2015-04-03T06:44:36+00:00

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call. We are way better off to have explicit
calls instead of this monstrosity.

Split out the tick_handover call and invoke it explicitely from
the hotplug code. Temporary solution will be cleaned up in later
patches.

Signed-off-by: Thomas Gleixner 
[ Rebase ]
Signed-off-by: Rafael J. Wysocki 
Cc: Peter Zijlstra 
Cc: John Stultz 
Cc: Linus Torvalds 
Cc: Andrew Morton 
Link: http://lkml.kernel.org/r/1658173.RkEEILFiQZ@vostro.rjw.lan
Signed-off-by: Ingo Molnar

clockevents: Provide explicit broadcast oneshot control functions

2015-04-03T06:44:33+00:00

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call. We are way better off to have explicit
calls instead of this monstrosity.

Split out the broadcast oneshot control into a separate function
and provide inline helpers. Switch clockevents_notify() over.
This will go away once all callers are converted.

This also gets rid of the nested locking of clockevents_lock and
broadcast_lock. The broadcast oneshot control functions do not
require clockevents_lock. Only the managing functions
(setup/shutdown/suspend/resume of the broadcast device require
clockevents_lock.

Signed-off-by: Thomas Gleixner 
Signed-off-by: Rafael J. Wysocki 
Cc: Alexandre Courbot 
Cc: Daniel Lezcano 
Cc: Len Brown 
Cc: Peter Zijlstra 
Cc: Stephen Warren 
Cc: Thierry Reding 
Cc: Tony Lindgren 
Link: http://lkml.kernel.org/r/13000649.8qZuEDV0OA@vostro.rjw.lan
Signed-off-by: Ingo Molnar

clockevents: Provide explicit broadcast control functions

2015-04-03T06:44:31+00:00

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call. We are way better off to have explicit
calls instead of this monstrosity.

Split out the broadcast control into a separate function and
provide inline helpers. Switch clockevents_notify() over. This
will go away once all callers are converted.

This also gets rid of the nested locking of clockevents_lock and
broadcast_lock. The broadcast control functions do not require
clockevents_lock. Only the managing functions
(setup/shutdown/suspend/resume of the broadcast device require
clockevents_lock.

Signed-off-by: Thomas Gleixner 
Signed-off-by: Rafael J. Wysocki 
Cc: Daniel Lezcano 
Cc: Len Brown 
Cc: Peter Zijlstra 
Cc: Tony Lindgren 
Link: http://lkml.kernel.org/r/8086559.ttsuS0n1Xr@vostro.rjw.lan
Signed-off-by: Ingo Molnar

tick: Further simplify tick-internal.h

2015-04-02T09:26:35+00:00

Move the broadcasting related section to the GENERIC_CLOCKEVENTS=y
section - this also solves build failures on architectures that
don't use generic clockevents yet.

Also standardize include file style to make it easier to read, and
use nesting depth aware preprocessor directives to make future merges
easier.

Cc: Peter Zijlstra 
Cc: Rafael J. Wysocki 
Cc: Thomas Gleixner 
Signed-off-by: Ingo Molnar

arm/bL_switcher: Kill tick suspend hackery

2015-04-01T12:23:00+00:00

Use the new tick_suspend/resume_local() and get rid of the
homebrewn implementation of these in the ARM bL switcher.  The
check for the cpumask is completely pointless.  There is no harm
to suspend a per cpu tick device unconditionally.  If that's a
real issue then we fix it proper at the core level and not with
some completely undocumented hacks in some random core code.

Move the tick internals to the core code, now that this nuisance
is gone.

Signed-off-by: Thomas Gleixner 
[ rjw: Rebase, changelog ]
Signed-off-by: Rafael J. Wysocki 
Cc: Nicolas Pitre 
Cc: Peter Zijlstra 
Cc: Russell King 
Link: http://lkml.kernel.org/r/1655112.Ws17YsMfN7@vostro.rjw.lan
Signed-off-by: Ingo Molnar

tick/xen: Provide and use tick_suspend_local() and tick_resume_local()

2015-04-01T12:23:00+00:00

Xen calls on every cpu into tick_resume() which is just wrong.
tick_resume() is for the syscore global suspend/resume
invocation. What XEN really wants is a per cpu local resume
function.

Provide a tick_resume_local() function and use it in XEN.

Also provide a complementary tick_suspend_local() and modify
tick_unfreeze() and tick_freeze(), respectively, to use the
new local tick resume/suspend functions.

Signed-off-by: Thomas Gleixner 
[ Combined two patches, rebased, modified subject/changelog. ]
Signed-off-by: Rafael J. Wysocki 
Cc: Boris Ostrovsky 
Cc: David Vrabel 
Cc: Konrad Rzeszutek Wilk 
Cc: Peter Zijlstra 
Link: http://lkml.kernel.org/r/1698741.eezk9tnXtG@vostro.rjw.lan
[ Merged to latest timers/core. ]
Signed-off-by: Ingo Molnar

tick: Make tick_resume_broadcast_oneshot() static

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

Solely used in tick-broadcast.c and the return value is
hardcoded 0. Make it static and void.

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

clockevents: Make suspend/resume calls explicit

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

clockevents_notify() is a leftover from the early design of the
clockevents facility. It's really not a notification mechanism,
it's a multiplex call.

We are way better off to have explicit calls instead of this
monstrosity. Split out the suspend/resume() calls and invoke
them directly from the call sites.

No locking required at this point because these calls happen
with interrupts disabled and a single cpu online.

Signed-off-by: Thomas Gleixner 
[ Rebased on top of 4.0-rc5. ]
Signed-off-by: Rafael J. Wysocki 
Cc: Peter Zijlstra 
Link: http://lkml.kernel.org/r/713674030.jVm1qaHuPf@vostro.rjw.lan
[ Rebased on top of latest timers/core. ]
Signed-off-by: Ingo Molnar

tick: Move core only declarations and functions to core

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

No point to expose everything to the world. People just believe
such functions can be abused for whatever purposes. Sigh.

Signed-off-by: Thomas Gleixner 
[ Rebased on top of 4.0-rc5 ]
Signed-off-by: Rafael J. Wysocki 
Cc: Nicolas Pitre 
Cc: Peter Zijlstra 
Link: http://lkml.kernel.org/r/28017337.VbCUc39Gme@vostro.rjw.lan
[ Merged to latest timers/core ]
Signed-off-by: Ingo Molnar