From: Waiman Long <llong@redhat.com>
To: Juri Lelli <juri.lelli@redhat.com>, Pingfan Liu <piliu@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Chen Ridong <chenridong@huaweicloud.com>,
Peter Zijlstra <peterz@infradead.org>,
Pierre Gondois <pierre.gondois@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCHv5] sched/deadline: Walk up cpuset hierarchy to decide root domain when hot-unplug
Date: Mon, 10 Nov 2025 16:07:27 -0500 [thread overview]
Message-ID: <5e0bb3f1-2efc-4302-aff0-80d5999c7700@redhat.com> (raw)
In-Reply-To: <aRHJHxfEI-tnotRe@jlelli-thinkpadt14gen4.remote.csb>
On 11/10/25 6:14 AM, Juri Lelli wrote:
> Hi,
>
> Looks like this has two issues.
>
> On 10/11/25 09:47, Pingfan Liu wrote:
>
> ...
>
>> +/*
>> + * This function always returns a non-empty bitmap in @cpus. This is because
>> + * if a root domain has reserved bandwidth for DL tasks, the DL bandwidth
>> + * check will prevent CPU hotplug from deactivating all CPUs in that domain.
>> + */
>> +static void dl_get_task_effective_cpus(struct task_struct *p, struct cpumask *cpus)
>> +{
>> + const struct cpumask *hk_msk;
>> +
>> + hk_msk = housekeeping_cpumask(HK_TYPE_DOMAIN);
>> + if (housekeeping_enabled(HK_TYPE_DOMAIN)) {
>> + if (!cpumask_intersects(p->cpus_ptr, hk_msk)) {
>> + /*
>> + * CPUs isolated by isolcpu="domain" always belong to
>> + * def_root_domain.
>> + */
>> + cpumask_andnot(cpus, cpu_active_mask, hk_msk);
>> + return;
>> + }
>> + }
>> +
>> + /*
>> + * If a root domain holds a DL task, it must have active CPUs. So
>> + * active CPUs can always be found by walking up the task's cpuset
>> + * hierarchy up to the partition root.
>> + */
>> + cpuset_cpus_allowed(p, cpus);
> Grabs callbak_lock spin_lock (sleepable on RT) under pi_lock
> raw_spin_lock.
I have been thinking about changing callback_lock to a raw_spinlock_t,
but need to find a good use case for this change. So it is a solvable
problem.
>> +}
>> +
>> +/* The caller should hold cpuset_mutex */
There is an upstream patch series that will add a helper function to
check if cpuset_mutex has been held. So this comment should be replaced
by a call to that helper function once it is available in the linux
mainline.
>> void dl_add_task_root_domain(struct task_struct *p)
>> {
>> struct rq_flags rf;
>> struct rq *rq;
>> struct dl_bw *dl_b;
>> + unsigned int cpu;
>> + struct cpumask msk;
> Potentially huge mask allocated on the stack.
Yes, we should use cpumask_var_t and call alloc_cpumask_var() before
acquiring lock.
Cheers,
Longman
>
>> raw_spin_lock_irqsave(&p->pi_lock, rf.flags);
>> if (!dl_task(p) || dl_entity_is_special(&p->dl)) {
>> @@ -2891,16 +2923,22 @@ void dl_add_task_root_domain(struct task_struct *p)
>> return;
>> }
>>
>> - rq = __task_rq_lock(p, &rf);
>> -
>> + /*
>> + * Get an active rq, whose rq->rd traces the correct root
>> + * domain.
>> + * And the caller should hold cpuset_mutex, which gurantees
>> + * the cpu remaining in the cpuset until rq->rd is fetched.
>> + */
>> + dl_get_task_effective_cpus(p, &msk);
>> + cpu = cpumask_first_and(cpu_active_mask, &msk);
>> + BUG_ON(cpu >= nr_cpu_ids);
>> + rq = cpu_rq(cpu);
>> dl_b = &rq->rd->dl_bw;
>> - raw_spin_lock(&dl_b->lock);
>>
>> + raw_spin_lock(&dl_b->lock);
>> __dl_add(dl_b, p->dl.dl_bw, cpumask_weight(rq->rd->span));
>> -
>> raw_spin_unlock(&dl_b->lock);
>> -
>> - task_rq_unlock(rq, p, &rf);
>> + raw_spin_unlock_irqrestore(&p->pi_lock, rf.flags);
> Thanks,
> Juri
>
next prev parent reply other threads:[~2025-11-10 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 1:47 Pingfan Liu
2025-11-10 11:14 ` Juri Lelli
2025-11-10 21:07 ` Waiman Long [this message]
2025-11-10 22:08 ` Waiman Long
2025-11-11 11:50 ` Pingfan Liu
2025-11-11 11:40 ` Pingfan Liu
2025-11-11 13:23 ` Juri Lelli
[not found] ` <da0dc9a7-ebbf-4078-8072-e75b3d7d2a5c@redhat.com>
2025-11-14 11:28 ` Pingfan Liu
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=5e0bb3f1-2efc-4302-aff0-80d5999c7700@redhat.com \
--to=llong@redhat.com \
--cc=bsegall@google.com \
--cc=chenridong@huaweicloud.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=piliu@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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 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®