Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932757AbbBPNLi (ORCPT ); Mon, 16 Feb 2015 08:11:38 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:38164 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932571AbbBPNJd (ORCPT ); Mon, 16 Feb 2015 08:09:33 -0500 Message-Id: <20150216122413.591402191@infradead.org> User-Agent: quilt/0.61-1 Date: Mon, 16 Feb 2015 13:15:02 +0100 From: Peter Zijlstra To: linux-kernel@vger.kernel.org, mingo@kernel.org, rjw@rjwysocki.net Cc: tglx@linutronix.de, peterz@infradead.org Subject: [PATCH 27/35] sched/idle: Use explicit broadcast oneshot control function References: <20150216121435.203983131@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline; filename=sched-idle-use-explicit-broadcast-oneshot-control-function.patch Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 39 From: Thomas Gleixner Replace the clockevents_notify() call with an explicit function call. Signed-off-by: Thomas Gleixner --- kernel/sched/idle.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) Index: linux/kernel/sched/idle.c =================================================================== --- linux.orig/kernel/sched/idle.c +++ linux/kernel/sched/idle.c @@ -143,8 +143,7 @@ use_default: * is used from another cpu as a broadcast timer, this call may * fail if it is not available */ - if (broadcast && - clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER, &dev->cpu)) + if (broadcast && tick_broadcast_enter()) goto use_default; /* Take note of the planned idle state. */ @@ -161,7 +160,7 @@ use_default: idle_set_state(this_rq(), NULL); if (broadcast) - clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_EXIT, &dev->cpu); + tick_broadcast_exit(); /* * Give the governor an opportunity to reflect on the outcome -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/