From: Frederic Weisbecker <frederic@kernel.org>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
John Stultz <john.stultz@linaro.org>,
Eric Dumazet <edumazet@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org, Arjan van de Ven <arjan@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Rik van Riel <riel@redhat.com>,
Richard Cochran <richardcochran@gmail.com>
Subject: Re: [PATCH v3 06/17] timer: Keep the pinned timers separate from the others
Date: Wed, 26 Oct 2022 17:26:21 +0200 [thread overview]
Message-ID: <20221026152621.GA1330257@lothringen> (raw)
In-Reply-To: <20221025135850.51044-7-anna-maria@linutronix.de>
On Tue, Oct 25, 2022 at 03:58:39PM +0200, Anna-Maria Behnsen wrote:
> @@ -1711,38 +1724,69 @@ u64 get_next_timer_interrupt(unsigned long basej, u64 basem)
> if (cpu_is_offline(smp_processor_id()))
> return expires;
>
> - raw_spin_lock(&base->lock);
> + base_local = this_cpu_ptr(&timer_bases[BASE_LOCAL]);
> + base_global = this_cpu_ptr(&timer_bases[BASE_GLOBAL]);
>
> - nextevt = next_timer_interrupt(base);
> + raw_spin_lock(&base_local->lock);
> + raw_spin_lock_nested(&base_global->lock, SINGLE_DEPTH_NESTING);
> +
> + nextevt_local = next_timer_interrupt(base_local);
> + nextevt_global = next_timer_interrupt(base_global);
>
> /*
> * We have a fresh next event. Check whether we can forward the
> * base. We can only do that when @basej is past base->clk
> * otherwise we might rewind base->clk.
> */
> - if (time_after(basej, base->clk)) {
> - if (time_after(nextevt, basej))
> - base->clk = basej;
> - else if (time_after(nextevt, base->clk))
> - base->clk = nextevt;
> + if (time_after(basej, base_local->clk)) {
> + if (time_after(nextevt_local, basej))
> + base_local->clk = basej;
> + else if (time_after(nextevt_local, base_local->clk))
> + base_local->clk = nextevt_local;
> + }
> +
> + if (time_after(basej, base_global->clk)) {
> + if (time_after(nextevt_global, basej))
> + base_global->clk = basej;
> + else if (time_after(nextevt_global, base_global->clk))
> + base_global->clk = nextevt_global;
Perhaps make a helper for the two above?
> }
>
> @@ -1763,6 +1807,9 @@ void timer_clear_idle(void)
> * the lock in the exit from idle path.
> */
> base->is_idle = false;
> +
> + base = this_cpu_ptr(&timer_bases[BASE_GLOBAL]);
> + base->is_idle = false;
May be just:
__this_cpu_write(timer_bases[BASE_LOCAL].is_idle, false)
__this_cpu_write(timer_bases[BASE_GLOBAL].is_idle, false)
> }
> #endif
>
> @@ -1820,17 +1869,21 @@ static __latent_entropy void run_timer_softirq(struct softirq_action *h)
> */
> static void run_local_timers(void)
> {
> - struct timer_base *base = this_cpu_ptr(&timer_bases[BASE_STD]);
> + struct timer_base *base = this_cpu_ptr(&timer_bases[BASE_LOCAL]);
>
> hrtimer_run_queues();
> /* Raise the softirq only if required. */
> if (time_before(jiffies, base->next_expiry)) {
> if (!IS_ENABLED(CONFIG_NO_HZ_COMMON))
> return;
> - /* CPU is awake, so check the deferrable base. */
> + /* CPU is awake, so check for the global base. */
> base++;
> - if (time_before(jiffies, base->next_expiry))
> - return;
> + if (time_before(jiffies, base->next_expiry)) {
> + /* CPU is awake, so check the deferrable base. */
> + base++;
> + if (time_before(jiffies, base->next_expiry))
> + return;
> + }
Could be:
for (i = 0; i < NR_BASES; i++) {
struct timer_base *base = this_cpu_ptr(&timer_bases[i]);
if (time_after_eq(jiffies, base->next_expiry)) {
raise_softirq(TIMER_SOFTIRQ);
return;
}
}
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
Thanks!
> }
> raise_softirq(TIMER_SOFTIRQ);
> }
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-10-26 15:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 13:58 [PATCH v3 00/17] timer: Move from a push remote at enqueue to a pull at expiry model Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 01/17] cpufreq: Prepare timer flags for hierarchical timer pull model Anna-Maria Behnsen
2022-10-26 13:54 ` Frederic Weisbecker
2022-10-31 15:22 ` Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 02/17] tick-sched: Warn when next tick seems to be in the past Anna-Maria Behnsen
2022-10-25 22:11 ` Frederic Weisbecker
2022-10-25 13:58 ` [PATCH v3 03/17] timer: Move store of next event into __next_timer_interrupt() Anna-Maria Behnsen
2022-10-26 9:33 ` Frederic Weisbecker
2022-10-25 13:58 ` [PATCH v3 04/17] timer: Split next timer interrupt logic Anna-Maria Behnsen
2022-10-26 9:40 ` Frederic Weisbecker
2022-10-25 13:58 ` [PATCH v3 05/17] timer: Rework idle logic Anna-Maria Behnsen
2022-10-26 13:27 ` Frederic Weisbecker
2022-10-25 13:58 ` [PATCH v3 06/17] timer: Keep the pinned timers separate from the others Anna-Maria Behnsen
2022-10-26 15:26 ` Frederic Weisbecker [this message]
2022-10-25 13:58 ` [PATCH v3 07/17] timer: Retrieve next expiry of pinned/non-pinned timers seperately Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 08/17] timer: Rename get_next_timer_interrupt() Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 09/17] timer: Split out "get next timer interrupt" functionality Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 10/17] timer: Add get next timer interrupt functionality for remote CPUs Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 11/17] timer: Restructure internal locking Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 12/17] timer: Check if timers base is handled already Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 13/17] tick/sched: Split out jiffies update helper function Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 14/17] timer: Implement the hierarchical pull model Anna-Maria Behnsen
2022-10-26 5:35 ` kernel test robot
2022-10-25 13:58 ` [PATCH v3 15/17] timer_migration: Add tracepoints Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 16/17] add_timer_on(): Make sure callers have TIMER_PINNED flag Anna-Maria Behnsen
2022-10-25 13:58 ` [PATCH v3 17/17] timer: Always queue timers on the local CPU Anna-Maria Behnsen
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=20221026152621.GA1330257@lothringen \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=arjan@infradead.org \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richardcochran@gmail.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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