[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <66c6e93c-1f9b-4252-8b28-3097565b81f3@amperemail.onmicrosoft.com>
Date: Tue, 16 Dec 2025 14:22:18 +0800
From: Shijie Huang <shijie@...eremail.onmicrosoft.com>
To: Vincent Guittot <vincent.guittot@...aro.org>,
Huang Shijie <shijie@...amperecomputing.com>
Cc: mingo@...hat.com, peterz@...radead.org, juri.lelli@...hat.com,
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, kprateek.nayak@....com
Subject: Re: [PATCH v6 2/2] sched: update the rq->avg_idle when a task is
moved to an idle CPU
On 13/12/2025 09:36, Vincent Guittot wrote:
> put_prev_task_idle() would be a better place to call
> update_rq_avg_idle() because this is when we leave idle.
The update_rq_avg_idle() is not only called by current CPU, but also
called by
other CPUs. For example, the try_to_wake_up(), update_rq_avg_idle() is
called by
the other CPUs. So enqueue_task() is a good place.
Thanks
Huang Shijie
Powered by blists - more mailing lists