Re: [PATCH v33 7/7] sched/proxy: Add deactivated (sleeping) owner handling to find_proxy_task()

[Juri Lelli]

Hello!

On 26/10/26 09:56, K Prateek Nayak wrote:
> On 10/24/2026 2:37 PM, Andrea Righi wrote:
> >> +static void do_activate_blocked_waiter(struct rq *target_rq, struct task_struct *p, int en_flags)
> >> +{

...

> >> +		if (task_cpu(p) != target_cpu) {
> >> +			en_flags |= ENQUEUE_MIGRATED;
> >> +			psi_ttwu_dequeue(p);
> >> +			proxy_set_task_cpu(p, target_cpu);
> >> +		}
> > 
> > Can this break SCHED_DEADLINE bw accounting?
> > 
> > p is sleeping here (not TASK_WAKING, not TASK_ON_RQ_MIGRATING), so
> > __set_task_cpu() skips migrate_task_rq_dl(): the old rq never does
> > sub_rq_bw(), while ENQUEUE_MIGRATED makes the new rq do add_rq_bw(), so
> > this_bw is leaked on the old rq. And if p is still dl_non_contending,
> > task_contending() on the new rq just cancels the inactive timer, leaving
> > running_bw on the old rq forever and making it underflow on the new rq
> > the next time p blocks.
> > 
> > set_task_cpu() doesn't help, because migrate_task_rq_dl() bails out
> > unless TASK_WAKING, so I'm not sure how to fix this case...
> 
> I wonder why "p->dl.dl_non_contending" is not sufficient to know if
> there exists residual bandwidth on prev CPU. Seems to have been like
> that since commit 209a0cbda7a0 ("sched/deadline: Improve the tracking
> of active utilization").
> 
> Only time task is non-contending is if it goes away with DEQUEUE_SLEEP
> or switched_from_dl() with dl_runtime.
> 
> The latter doesn't need migrating the timer as the timer will either
> be cancelled if the task switches back to deadline, or will expire
> where it was queued - set_task_cpu() has no effect in this case.
> 
> Only other case that marks "dl_non_contending" is sleep + wakeup and
> for that "p->dl.non_contending" should be sufficient. I don't think
> we ever do a set_task_cpu() for a blocked task other than wakeup do
> we?
> 
> Juri, Peter, are we missing something subtle here?

I think Andrea's concern is valid, but I'm not sure I follow what you
propose Prateek (apologies!) or are you saying you don't see an issue
here?

If the issue is confirmed, I wonder if relaxing the first check in
migrate_task_rq_dl() to something like

    if (READ_ONCE(p->__state) != TASK_WAKING && !p->is_blocked)
        return;

might fix things, but then it's ugly to call it from do_activate_
blocked_waiter(). We could teach set_task_cpu() about blocked waiters
(otherwise it warns) and then call it instead of __set_task_cpu(), but
I'm not sure it's any prettier.

Thanks,
Juri