mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	 Thomas Gleixner <tglx@linutronix.de>,
	Waiman Long <longman@redhat.com>
Subject: Re: [PATCH v8 7/7] timers: Exclude isolated cpus from timer migration
Date: Fri, 25 Jul 2025 08:42:19 +0200	[thread overview]
Message-ID: <381cb8d6b28648dbd5772c6bc0b2f1f10c29b53d.camel@redhat.com> (raw)
In-Reply-To: <aIK8UFz3A7hNc1sq@pavilion.home>

On Fri, 2025-07-25 at 01:05 +0200, Frederic Weisbecker wrote:
> 
> And this is basically repeating the same logic as before but in
> reverse.
> 
> Here is a proposal: register the online/offline callbacks later, on
> late_initcall(). This solves two problems:
> 
> 1) The online/offline callbacks are called for the first time in the
> right
>    place. You don't need that tmigr_exclude_isolated anymore.
> 
> 2) You don't need to make the on_each_cpu_cond_mask() call anymore in
>    tmigr_init_isolation(). In fact you don't need that function. The
>    online/offline callbacks already take care of everything.
> 

Yeah, that's much neater thanks!
I'm going to try it and update the patch.

> Here is a patch you can use (only built tested):
> 
> commit ad21e35e05865e2d37a60bf5d77b0d6fa22a54ee
> Author: Frederic Weisbecker <frederic@kernel.org>
> Date:   Fri Jul 25 00:06:20 2025 +0200
> 
>     timers/migration: Postpone online/offline callbacks registration
> to late initcall    
>     During the early boot process, the default clocksource used for
>     timekeeping is the jiffies. Better clocksources can only be
> selected once clocksource_done_booting() is called as an fs initcall.
>     
>     NOHZ can only be enabled after that stage, making global timer
> migration irrelevant up to that point.
>     
>     Therefore, don't bother with trashing the cache within that tree
> from the SMP bootup until NOHZ even matters.
>     
>     Make the CPUs available to the tree on late initcall, after the
> right clocksource had a chance to be selected. This will also
> simplify the handling of domain isolated CPUs on further patches.
>     
>     Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> 

I assume it's cleaner if I squash it in 7/7 and add a
Co-developed-by: Frederic Weisbecker <frederic@kernel.org>
and/or
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>

Do you agree?

Thanks for the review and help,
Gabriele

> diff --git a/kernel/time/timer_migration.c
> b/kernel/time/timer_migration.c
> index 2f6330831f08..f730107d948d 100644
> --- a/kernel/time/timer_migration.c
> +++ b/kernel/time/timer_migration.c
> @@ -1484,6 +1484,17 @@ static int tmigr_cpu_online(unsigned int cpu)
>  	return 0;
>  }
>  
> +/*
> + * NOHZ can only be enabled after clocksource_done_booting(). Don't
> + * bother trashing the cache in the tree before.
> + */
> +static int __init tmigr_late_init(void)
> +{
> +	return cpuhp_setup_state(CPUHP_AP_TMIGR_ONLINE,
> "tmigr:online",
> +				 tmigr_cpu_online,
> tmigr_cpu_offline);
> +}
> +late_initcall(tmigr_late_init);
> +
>  static void tmigr_init_group(struct tmigr_group *group, unsigned int
> lvl,
>  			     int node)
>  {
> @@ -1846,18 +1857,9 @@ static int __init tmigr_init(void)
>  
>  	ret = cpuhp_setup_state(CPUHP_TMIGR_PREPARE,
> "tmigr:prepare",
>  				tmigr_cpu_prepare, NULL);
> -	if (ret)
> -		goto err;
> -
> -	ret = cpuhp_setup_state(CPUHP_AP_TMIGR_ONLINE,
> "tmigr:online",
> -				tmigr_cpu_online,
> tmigr_cpu_offline);
> -	if (ret)
> -		goto err;
> -
> -	return 0;
> -
>  err:
> -	pr_err("Timer migration setup failed\n");
> +	if (ret)
> +		pr_err("Timer migration setup failed\n");
>  	return ret;
>  }
>  early_initcall(tmigr_init);


  reply	other threads:[~2025-07-25  6:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 13:30 [PATCH v8 0/7] " Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 1/7] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 2/7] timers: Add the available mask in timer migration Gabriele Monaco
2025-07-24 10:20   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 3/7] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-07-24 10:29   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 4/7] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-07-24 10:33   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 5/7] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-07-14 13:30 ` [PATCH v8 6/7] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-07-24 13:01   ` Frederic Weisbecker
2025-07-14 13:30 ` [PATCH v8 7/7] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-07-24 23:05   ` Frederic Weisbecker
2025-07-25  6:42     ` Gabriele Monaco [this message]
2025-07-25 10:55       ` Frederic Weisbecker

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=381cb8d6b28648dbd5772c6bc0b2f1f10c29b53d.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@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

all inboxes | Powered by JetHome®