From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: [patch 01/10] timer: Invoke timer_start_debug() where it makes sense Date: Mon, 17 Apr 2017 20:32:42 +0200 Message-ID: <20170417184356.042505603@linutronix.de> References: <20170417183241.244217993@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Return-path: Content-Disposition: inline; filename=timer--call-debug-function-after-setting-properly-the-base-and-the-flags.patch Sender: linux-kernel-owner@vger.kernel.org To: LKML Cc: Peter Zijlstra , John Stultz , Eric Dumazet , Anna-Maria Gleixner , "Rafael J. Wysocki" , linux-pm@vger.kernel.org, Arjan van de Ven , "Paul E. McKenney" , Frederic Weisbecker , Rik van Riel List-Id: linux-pm@vger.kernel.org The timer start debug function is called before the proper timer base is set. As a consequence the trace data contains the stale CPU and flags values. Call the debug function after setting the new base and flags. Signed-off-by: Anna-Maria Gleixner Signed-off-by: Thomas Gleixner --- kernel/time/timer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/kernel/time/timer.c +++ b/kernel/time/timer.c @@ -970,8 +970,6 @@ static inline int if (!ret && pending_only) goto out_unlock; - debug_activate(timer, expires); - new_base = get_target_base(base, timer->flags); if (base != new_base) { @@ -994,6 +992,8 @@ static inline int } } + debug_activate(timer, expires); + /* Try to forward a stale timer base clock */ forward_timer_base(base);