linux-kernel - Re: [PATCH v3 2/2] sched: update the rq->avg_idle when a task is moved to an idle CPU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5aef850b-86b5-45f7-81ef-d1d08fd2a673@amperemail.onmicrosoft.com>
Date: Fri, 28 Nov 2025 14:30:03 +0800
From: Shijie Huang <shijie@...eremail.onmicrosoft.com>
To: K Prateek Nayak <kprateek.nayak@....com>,
 Huang Shijie <shijie@...amperecomputing.com>, mingo@...hat.com,
 peterz@...radead.org, juri.lelli@...hat.com, vincent.guittot@...aro.org
Cc: patches@...erecomputing.com, cl@...ux.com,
 Shubhang@...amperecomputing.com, dietmar.eggemann@....com,
 rostedt@...dmis.org, bsegall@...gle.com, mgorman@...e.de,
 linux-kernel@...r.kernel.org, vschneid@...hat.com, vineethr@...ux.ibm.com
Subject: Re: [PATCH v3 2/2] sched: update the rq->avg_idle when a task is
 moved to an idle CPU


On 27/11/2025 18:12, K Prateek Nayak wrote:
> Also if we've done newidle balance and the rq->idle_stamp is
> set, we cannot have delayed tasks since pick_next_task() would
> have dequeued all delayed tasks before reaching newidle
> balance.
Yes, you are right.
> Just doing a update_rq_avg_idle() unconditionally should be
> fine.

okay.


Thanks

Huang Shijie