linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv5 01/11] clockevents: Prefer CPU local devices over global devices
Date: Fri, 19 Apr 2013 09:19:35 -0700	[thread overview]
Message-ID: <1366388385-30722-2-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1366388385-30722-1-git-send-email-sboyd@codeaurora.org>

On an SMP system with only one global clockevent and a dummy
clockevent per CPU we run into problems. We want the dummy
clockevents to be registered as the per CPU tick devices, but
we can only achieve that if we register the dummy clockevents
before the global clockevent or if we artificially inflate the
rating of the dummy clockevents to be higher than the rating
of the global clockevent. Failure to do so leads to boot
hangs when the dummy timers are registered on all other CPUs
besides the CPU that accepted the global clockevent as its tick
device and there is no broadcast timer to poke the dummy
devices.

If we're registering multiple clockevents and one clockevent is
global and the other is local to a particular CPU we should
choose to use the local clockevent regardless of the rating of
the device. This way, if the clockevent is a dummy it will take
the tick device duty as long as there isn't a higher rated tick
device and any global clockevent will be bumped out into
broadcast mode, fixing the problem described above.

Reported-by: Mark Rutland <mark.rutland@arm.com>
Tested-by: Mark Rutland <mark.rutland@arm.com>
Cc: John Stultz <john.stultz@linaro.org>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
 kernel/time/tick-common.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c
index 412bcef..d616eca 100644
--- a/kernel/time/tick-common.c
+++ b/kernel/time/tick-common.c
@@ -254,9 +254,10 @@ static int tick_check_new_device(struct clock_event_device *newdev)
 		    !(newdev->features & CLOCK_EVT_FEAT_ONESHOT))
 			goto out_bc;
 		/*
-		 * Check the rating
+		 * Check the rating, but prefer CPU local devices
 		 */
-		if (curdev->rating >= newdev->rating)
+		if (curdev->rating >= newdev->rating &&
+		    cpumask_equal(curdev->cpumask, newdev->cpumask))
 			goto out_bc;
 	}
 
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-04-19 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 16:19 [PATCHv5 00/11] Remove ARM local timer API Stephen Boyd
2013-04-19 16:19 ` Stephen Boyd [this message]
2013-04-19 16:19 ` [PATCHv5 02/11] clocksource: add generic dummy timer driver Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 03/11] ARM: smp: Remove duplicate dummy timer implementation Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 04/11] ARM: smp_twd: Divorce smp_twd from local timer API Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 05/11] ARM: OMAP2+: Divorce " Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 06/11] ARM: EXYNOS4: Divorce mct " Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 07/11] ARM: PRIMA2: Divorce timer-marco " Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 08/11] ARM: msm: Divorce msm_timer " Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 09/11] clocksource: time-armada-370-xp: Fix sparse warning Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 10/11] clocksource: time-armada-370-xp: Divorce from local timer API Stephen Boyd
2013-04-19 16:19 ` [PATCHv5 11/11] ARM: smp: Remove " Stephen Boyd
2013-04-22  2:26 ` [PATCHv5 00/11] Remove ARM " Barry Song

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1366388385-30722-2-git-send-email-sboyd@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).