From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: Huang Shijie <shijie@os.amperecomputing.com>
Cc: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, patches@amperecomputing.com,
cl@linux.com, Shubhang@os.amperecomputing.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org, vschneid@redhat.com,
kprateek.nayak@amd.com,
Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Subject: Re: [PATCH v4 1/2] sched/fair: set rq->idle_stamp at the end of the sched_balance_newidle
Date: Fri, 28 Nov 2025 15:37:44 +0530 [thread overview]
Message-ID: <1b0facef-8d3c-45fa-a490-506204e1395d@linux.ibm.com> (raw)
In-Reply-To: <20251128075454.676765-2-shijie@os.amperecomputing.com>
Hi Huang,
On 28/11/25 13:24, Huang Shijie wrote:
> Save the idle_stamp at the beginning of sched_balance_newidle(),
> if it cannot pull any task, set it for rq->idle_stamp.
>
> This patch does not change the logic of rq->idle_stamp.
>
> Signed-off-by: Huang Shijie <shijie@os.amperecomputing.com>
> ---
> kernel/sched/fair.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 769d7b7990df..c1a8fa043156 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -12862,6 +12862,7 @@ static int sched_balance_newidle(struct rq *this_rq, struct rq_flags *rf)
> u64 t0, t1, curr_cost = 0;
> struct sched_domain *sd;
> int pulled_task = 0;
> + u64 idle_stamp;
>
> update_misfit_status(NULL, this_rq);
>
> @@ -12877,7 +12878,9 @@ static int sched_balance_newidle(struct rq *this_rq, struct rq_flags *rf)
> * for CPU_NEWLY_IDLE, such that we measure the this duration
> * as idle time.
> */
> - this_rq->idle_stamp = rq_clock(this_rq);
> + idle_stamp = rq_clock(this_rq);
> +
> + this_rq->idle_stamp = 0;
IIUC, by setting this_rq->idle_stamp = 0 at the beginning, any call to update_rq_avg_idle() during
load balancing when tasks are pulled will fail the if (rq->idle_stamp) check, preventing the average
idle time from being updated.
Thanks,
Vineeth
>
> /*
> * Do not pull tasks towards !active CPUs...
> @@ -12989,10 +12992,11 @@ static int sched_balance_newidle(struct rq *this_rq, struct rq_flags *rf)
> if (time_after(this_rq->next_balance, next_balance))
> this_rq->next_balance = next_balance;
>
> - if (pulled_task)
> - this_rq->idle_stamp = 0;
> - else
> + if (!pulled_task) {
> + /* Set it here on purpose. */
> + this_rq->idle_stamp = idle_stamp;
> nohz_newidle_balance(this_rq);
> + }
>
> rq_repin_lock(this_rq, rf);
>
next prev parent reply other threads:[~2025-11-28 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 7:54 [PATCH v4 0/2] sched: update the rq->avg_idle when a task is moved to an idle CPU Huang Shijie
2025-11-28 7:54 ` [PATCH v4 1/2] sched/fair: set rq->idle_stamp at the end of the sched_balance_newidle Huang Shijie
2025-11-28 9:31 ` Peter Zijlstra
2025-12-01 2:48 ` Shijie Huang
2025-11-28 10:07 ` Madadi Vineeth Reddy [this message]
2025-11-28 12:54 ` Shijie Huang
2025-11-28 13:01 ` Shijie Huang
2025-11-28 7:54 ` [PATCH v4 2/2] sched: update the rq->avg_idle when a task is moved to an idle CPU Huang Shijie
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=1b0facef-8d3c-45fa-a490-506204e1395d@linux.ibm.com \
--to=vineethr@linux.ibm.com \
--cc=Shubhang@os.amperecomputing.com \
--cc=bsegall@google.com \
--cc=cl@linux.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=patches@amperecomputing.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shijie@os.amperecomputing.com \
--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