From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/twd: avoid waking deeply sleeping CPUs for rate change notifier
Date: Mon, 11 Jun 2018 18:16:01 +0200 [thread overview]
Message-ID: <1528733761.2842.8.camel@pengutronix.de> (raw)
In-Reply-To: <20180417104627.29643-1-l.stach@pengutronix.de>
Hi all,
Am Dienstag, den 17.04.2018, 12:46 +0200 schrieb Lucas Stach:
> The current clock notifier sends an IPI to all CPUs, even if they are in
> deep sleep state with the local timer disabled and switched to tick
> broadcast. This needlessly cuts the CPU sleep times, as nothing is gained
> from updating a disabled TWDs rate.
>
> Keep track of the enabled TWDs and only send an IPI to those CPUs with an
> active local timer. As disabled TWDs may now miss a CPU frequency update
> we need to make sure to refresh the rate on re-enabling of the timer.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
I would appreciate some feedback to this patch.
FWIW, I've been running some systems with this patch applied for quite
some time now with no issues spotted so far.
Regards,
Lucas
> ---
> ?arch/arm/kernel/smp_twd.c | 31 +++++++++++++++++++++++++++++--
> ?1 file changed, 29 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/kernel/smp_twd.c b/arch/arm/kernel/smp_twd.c
> index b30eafeef096..a3be30d30cc2 100644
> --- a/arch/arm/kernel/smp_twd.c
> +++ b/arch/arm/kernel/smp_twd.c
> @@ -32,6 +32,8 @@ static struct clk *twd_clk;
> ?static unsigned long twd_timer_rate;
> ?static DEFINE_PER_CPU(bool, percpu_setup_called);
> ?
> +static cpumask_var_t active_twd_mask;
> +
> ?static struct clock_event_device __percpu *twd_evt;
> ?static unsigned int twd_features =
> > ? CLOCK_EVT_FEAT_PERIODIC | CLOCK_EVT_FEAT_ONESHOT;
> @@ -39,12 +41,24 @@ static int twd_ppi;
> ?
> ?static int twd_shutdown(struct clock_event_device *clk)
> ?{
> > + cpumask_clear_cpu(smp_processor_id(), active_twd_mask);
> +
> > ? writel_relaxed(0, twd_base + TWD_TIMER_CONTROL);
> > ? return 0;
> ?}
> ?
> ?static int twd_set_oneshot(struct clock_event_device *clk)
> ?{
> > + cpumask_set_cpu(smp_processor_id(), active_twd_mask);
> +
> > + /*
> > + ?* When going from shutdown to oneshot we might have missed some
> > + ?* frequency updates if the CPU was sleeping. Make sure to update
> > + ?* the timer frequency with the current rate.
> > + ?*/
> > + if (clockevent_state_shutdown(clk))
> > + clockevents_update_freq(clk, twd_timer_rate);
> +
> > ? /* period set, and timer enabled in 'next_event' hook */
> > ? writel_relaxed(TWD_TIMER_CONTROL_IT_ENABLE | TWD_TIMER_CONTROL_ONESHOT,
> > ? ???????twd_base + TWD_TIMER_CONTROL);
> @@ -57,6 +71,16 @@ static int twd_set_periodic(struct clock_event_device *clk)
> > ? ?????TWD_TIMER_CONTROL_IT_ENABLE |
> > ? ?????TWD_TIMER_CONTROL_PERIODIC;
> ?
> > + cpumask_set_cpu(smp_processor_id(), active_twd_mask);
> +
> > + /*
> > + ?* When going from shutdown to periodic we might have missed some
> > + ?* frequency updates if the CPU was sleeping. Make sure to update
> > + ?* the timer frequency with the current rate.
> > + ?*/
> > + if (clockevent_state_shutdown(clk))
> > + clockevents_update_freq(clk, twd_timer_rate);
> +
> > ? writel_relaxed(DIV_ROUND_CLOSEST(twd_timer_rate, HZ),
> > ? ???????twd_base + TWD_TIMER_LOAD);
> > ? writel_relaxed(ctrl, twd_base + TWD_TIMER_CONTROL);
> @@ -124,8 +148,8 @@ static int twd_rate_change(struct notifier_block *nb,
> > ? ?* changing cpu.
> > ? ?*/
> > ? if (flags == POST_RATE_CHANGE)
> > - on_each_cpu(twd_update_frequency,
> > - ??(void *)&cnd->new_rate, 1);
> > + on_each_cpu_mask(active_twd_mask, twd_update_frequency,
> > + ?(void *)&cnd->new_rate, 1);
> ?
> > ? return NOTIFY_OK;
> ?}
> @@ -326,6 +350,9 @@ static int __init twd_local_timer_common_register(struct device_node *np)
> ?{
> > ? int err;
> ?
> > + if (!zalloc_cpumask_var(&active_twd_mask, GFP_KERNEL))
> > + return -ENOMEM;
> +
> > ? twd_evt = alloc_percpu(struct clock_event_device);
> > ? if (!twd_evt) {
> > ? err = -ENOMEM;
next prev parent reply other threads:[~2018-06-11 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 10:46 [PATCH] arm/twd: avoid waking deeply sleeping CPUs for rate change notifier Lucas Stach
2018-06-11 16:16 ` Lucas Stach [this message]
2018-10-29 11:34 ` Lucas Stach
2018-10-29 12:30 ` Daniel Lezcano
2018-11-06 17:25 ` Russell King - ARM Linux
2018-11-18 1:48 ` Daniel Lezcano
2018-11-06 16:29 ` Philipp Zabel
-- strict thread matches above, loose matches on Subject: below --
2019-12-02 16:45 Lucas Stach
2019-12-05 20:29 ` Daniel Lezcano
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=1528733761.2842.8.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--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).