From: Frederic Weisbecker <frederic@kernel.org>
To: Gabriele Monaco <gmonaco@redhat.com>
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 v7 2/7] timers: Add the available mask in timer migration
Date: Mon, 7 Jul 2025 13:11:34 +0200 [thread overview]
Message-ID: <aGurZkPohjZ0pRwX@localhost.localdomain> (raw)
In-Reply-To: <20250626114900.106061-3-gmonaco@redhat.com>
Le Thu, Jun 26, 2025 at 01:48:55PM +0200, Gabriele Monaco a écrit :
> Keep track of the CPUs available for timer migration in a cpumask. This
> prepares the ground to generalise the concept of unavailable CPUs.
>
> Signed-off-by: Gabriele Monaco <gmonaco@redhat.com>
> ---
> kernel/time/timer_migration.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/time/timer_migration.c b/kernel/time/timer_migration.c
> index 2c2c8810b8137..2ec003c2bbbea 100644
> --- a/kernel/time/timer_migration.c
> +++ b/kernel/time/timer_migration.c
> @@ -422,6 +422,9 @@ static unsigned int tmigr_crossnode_level __read_mostly;
>
> static DEFINE_PER_CPU(struct tmigr_cpu, tmigr_cpu);
>
> +/* CPUs available for timer migration */
> +static cpumask_var_t tmigr_available_cpumask;
> +
> #define TMIGR_NONE 0xFF
> #define BIT_CNT 8
>
> @@ -1449,6 +1452,7 @@ static int tmigr_clear_cpu_available(unsigned int cpu)
> raw_spin_lock_irq(&tmc->lock);
> tmc->available = false;
> WRITE_ONCE(tmc->wakeup, KTIME_MAX);
> + cpumask_clear_cpu(cpu, tmigr_available_cpumask);
This is under the tmc lock.
>
> /*
> * CPU has to handle the local events on his own, when on the way to
> @@ -1459,7 +1463,7 @@ static int tmigr_clear_cpu_available(unsigned int cpu)
> raw_spin_unlock_irq(&tmc->lock);
>
> if (firstexp != KTIME_MAX) {
> - migrator = cpumask_any_but(cpu_online_mask, cpu);
> + migrator = cpumask_any(tmigr_available_cpumask);
But this is not.
We should make it clear what synchronizes the accesses to
tmigr_available_cpumask.
ie: we expect that either the cpu_hotplug_lock is write-held, or
it's read-held and cpuset_mutex is held.
But tmc->lock is not helpful. So the cpumask should be outside that
lock to avoid confusion.
Thanks.
> work_on_cpu(migrator, tmigr_trigger_active, NULL);
> }
>
> @@ -1480,6 +1484,7 @@ static int tmigr_set_cpu_available(unsigned int cpu)
> if (!tmc->idle)
> __tmigr_cpu_activate(tmc);
> tmc->available = true;
> + cpumask_set_cpu(cpu, tmigr_available_cpumask);
> raw_spin_unlock_irq(&tmc->lock);
> return 0;
> }
> @@ -1801,6 +1806,11 @@ static int __init tmigr_init(void)
> if (ncpus == 1)
> return 0;
>
> + if (!zalloc_cpumask_var(&tmigr_available_cpumask, GFP_KERNEL)) {
> + ret = -ENOMEM;
> + goto err;
> + }
> +
> /*
> * Calculate the required hierarchy levels. Unfortunately there is no
> * reliable information available, unless all possible CPUs have been
> --
> 2.49.0
>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2025-07-07 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 11:48 [PATCH v7 0/7] timers: Exclude isolated cpus from " Gabriele Monaco
2025-06-26 11:48 ` [PATCH v7 1/7] timers: Rename tmigr 'online' bit to 'available' Gabriele Monaco
2025-07-07 10:12 ` Frederic Weisbecker
2025-06-26 11:48 ` [PATCH v7 2/7] timers: Add the available mask in timer migration Gabriele Monaco
2025-07-07 11:11 ` Frederic Weisbecker [this message]
2025-06-26 11:48 ` [PATCH v7 3/7] timers: Use scoped_guard when setting/clearing the tmigr available flag Gabriele Monaco
2025-06-26 11:48 ` [PATCH v7 4/7] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_exclusion_cpumasks() Gabriele Monaco
2025-06-26 11:48 ` [PATCH v7 5/7] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-07-07 11:28 ` Frederic Weisbecker
2025-06-26 11:48 ` [PATCH v7 6/7] cgroup/cpuset: Fail if isolated and nohz_full don't leave any housekeeping Gabriele Monaco
2025-06-26 11:49 ` [PATCH v7 7/7] timers: Exclude isolated cpus from timer migration Gabriele Monaco
2025-07-07 13:11 ` 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=aGurZkPohjZ0pRwX@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=gmonaco@redhat.com \
--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®