From: Thomas Gleixner <tglx@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>,
linux-kernel@vger.kernel.org,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
Waiman Long <longman@redhat.com>
Cc: "John B. Wyatt IV" <jwyatt@redhat.com>,
"John B. Wyatt IV" <sageofredondo@gmail.com>
Subject: Re: [PATCH v16 7/7] timers/migration: Exclude isolated cpus from hierarchy
Date: Thu, 20 Nov 2025 16:34:42 +0100 [thread overview]
Message-ID: <87jyzkk99p.ffs@tglx> (raw)
In-Reply-To: <0c5d224858b31f66a9a166c990a393cb2a121162.camel@redhat.com>
On Thu, Nov 20 2025 at 16:23, Gabriele Monaco wrote:
> On Thu, 2025-11-20 at 16:21 +0100, Thomas Gleixner wrote:
>> On Thu, Nov 20 2025 at 15:56, Gabriele Monaco wrote:
>> > + * This function returns false during early boot and the isolation logic is
>> > + * enabled only after isolated CPUs are marked as unavailable at late boot.
>> > + * The tick CPU can be isolated at boot, however we cannot mark it as
>> > + * unavailable to avoid having no global migrator for the nohz_full CPUs.
>> > This
>> > + * should be ensured by the callers of this function: implicitly from
>> > hotplug
>> > + * callbacs and explicitly in tmigr_init_isolation() and
>>
>> 'callbacs' is still not correct :)
>>
>> Other than that:
>>
>> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>
> Damn, I knew I was missing something..
> Should I send a v17 for this or just re-send this patch?
That'll be fixed up when applying. I wait for Frederic to review it
first.
next prev parent reply other threads:[~2025-11-20 15:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 14:56 [PATCH v16 0/7] timers/migration: Exclude isolated cpus from hierarchy Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 1/7] timers/migration: Rename 'online' bit to 'available' Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 2/7] timers/migration: Add mask for CPUs available in the hierarchy Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 3/7] timers/migration: Use scoped_guard on available flag set/clear Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 4/7] cgroup/cpuset: Rename update_unbound_workqueue_cpumask() to update_isolation_cpumasks() Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 5/7] sched/isolation: Force housekeeping if isolcpus and nohz_full don't leave any Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
2025-11-20 14:56 ` [PATCH v16 6/7] cpumask: Add initialiser to use cleanup helpers Gabriele Monaco
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Yury Norov
2025-11-20 14:56 ` [PATCH v16 7/7] timers/migration: Exclude isolated cpus from hierarchy Gabriele Monaco
2025-11-20 15:21 ` Thomas Gleixner
2025-11-20 15:23 ` Gabriele Monaco
2025-11-20 15:34 ` Thomas Gleixner [this message]
2025-11-20 16:12 ` Frederic Weisbecker
2025-11-20 19:18 ` Thomas Gleixner
2025-11-20 19:22 ` [tip: timers/core] " tip-bot2 for Gabriele Monaco
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=87jyzkk99p.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=gmonaco@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=sageofredondo@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.