From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] tick: broadcast-hrtimer: use cpu_possible_mask for ce_broadcast_hrtimer
Date: Wed, 11 Jul 2018 12:24:23 +0100 [thread overview]
Message-ID: <1531308264-24220-2-git-send-email-sudeep.holla@arm.com> (raw)
In-Reply-To: <1531308264-24220-1-git-send-email-sudeep.holla@arm.com>
This is the last instance of cpu_all_mask usage in the core framework.
Lets replace it with cpu_possible_mask like all other instances in the
clockevent drivers. This will now enable us to add warning in the core
clockevents_register_device on usage of cpu_all_mask from any clockevent
drivers in future.
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
---
kernel/time/tick-broadcast-hrtimer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/time/tick-broadcast-hrtimer.c b/kernel/time/tick-broadcast-hrtimer.c
index 58045eb976c3..a59641fb88b6 100644
--- a/kernel/time/tick-broadcast-hrtimer.c
+++ b/kernel/time/tick-broadcast-hrtimer.c
@@ -90,7 +90,7 @@ static struct clock_event_device ce_broadcast_hrtimer = {
.max_delta_ticks = ULONG_MAX,
.mult = 1,
.shift = 0,
- .cpumask = cpu_all_mask,
+ .cpumask = cpu_possible_mask,
};
static enum hrtimer_restart bc_handler(struct hrtimer *t)
--
2.7.4
next prev parent reply other threads:[~2018-07-11 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 11:24 [PATCH 1/3] clocksource: drivers: set clockevent device cpumask to cpu_possible_mask Sudeep Holla
2018-07-11 11:24 ` Sudeep Holla [this message]
2018-07-11 11:24 ` [PATCH 3/3] clockevents: warn if cpu_all_mask is used for cpumask while registering new device Sudeep Holla
2018-08-02 12:39 ` Sudeep Holla
2018-07-11 11:36 ` [PATCH 1/3] clocksource: drivers: set clockevent device cpumask to cpu_possible_mask Daniel Lezcano
2018-07-11 13:42 ` Sudeep Holla
2018-07-11 16:38 ` Daniel Lezcano
2018-07-13 22:45 ` Thomas Gleixner
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=1531308264-24220-2-git-send-email-sudeep.holla@arm.com \
--to=sudeep.holla@arm.com \
--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).