mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Peter Zijlstra <peterz@infradead.org>, John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	David Stevens <stevensd@google.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Juri Lelli" <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Valentin Schneider <vschneid@redhat.com>,
	Suleiman Souhlal <suleiman@google.com>,
	Andrea Righi <arighi@nvidia.com>, Metin Kaya <Metin.Kaya@arm.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	Zimuzo Ezeozue <zezeozue@google.com>,
	"Waiman Long" <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Joel Fernandes <joelagnelf@nvidia.com>,
	"Qais Yousef" <qyousef@layalina.io>,
	Xuewen Yan <xuewen.yan94@gmail.com>,
	kuyo chang <kuyo.chang@mediatek.com>, hupu <hupu.gm@gmail.com>,
	Zhan Xusheng <zhanxusheng@xiaomi.com>,
	"zhidao su (Xiaomi)" <soolaugust@gmail.com>,
	Hui Su <sh_def@163.com>,
	"Shubhang Kaushik (Ampere)" <sh@gentwo.org>,
	<kernel-team@android.com>
Subject: Re: [PATCH v33 1/7] sched/psi: Preserve sleep-persistent PSI flags on off-CPU sleeping dequeues
Date: Mon, 26 Oct 2026 10:30:01 +0530	[thread overview]
Message-ID: <58521a9f-2f05-4176-8b14-96c7b5f0e212@amd.com> (raw)
In-Reply-To: <20261024114422.GA6775@noisy.programming.kicks-ass.net>

Hello Peter,

On 10/24/2026 5:14 PM, Peter Zijlstra wrote:
> On Fri, Oct 23, 2026 at 10:04:12PM +0000, John Stultz wrote:
>> diff --git a/kernel/sched/stats.h b/kernel/sched/stats.h
>> index ebe0a7765f98e..20820fe1021a1 100644
>> --- a/kernel/sched/stats.h
>> +++ b/kernel/sched/stats.h
>> @@ -175,12 +175,28 @@ static inline void psi_dequeue(struct task_struct *p, int flags)
>>  	 * Do nothing here.
>>  	 *
>>  	 * In the SCHED_PROXY_EXECUTION case we may do sleeping
>> -	 * dequeues that are not followed by a task switch, so check
>> -	 * TSK_ONCPU is set to ensure the task switch is imminent.
>> -	 * Otherwise clear the flags as usual.
>> +	 * dequeues that are not followed by a task switch. If TSK_ONCPU
>> +	 * is not set (meaning we already switched away while the task
>> +	 * stayed on the rq as a blocked donor), handle the sleeping
>> +	 * state transition here so sleep-persistent states (TSK_MEMSTALL,
>> +	 * TSK_IOWAIT) are preserved.
>>  	 */
>> -	if ((flags & DEQUEUE_SLEEP) && (p->psi_flags & TSK_ONCPU))
>> +	if (flags & DEQUEUE_SLEEP) {
>> +		int clear = TSK_RUNNING, set = 0;
>> +
>> +		if (p->psi_flags & TSK_ONCPU)
>> +			return;
>> +		if (p->se.sched_delayed)
>> +			return;
> 
> Must this really be sched_delayed, that is, cannot p->is_blocked be used
> here? I'm trying to push sched_delayed into fair.c if at all possible.

In this case, blocked donors going to sleep would need
to set the PSI flags accordingly (do what psi_sched_switch()
missed).

"p->se.sched_delayed" tasks would have already set those indicators
but can still arrive here from dequeue_task(SLEEP | DELAYED) of
sched_change_begin() - in all those cases, the dequeue flags will
also have DEQUEUE_DELAYED which can be used instead to bail out
early here.

Would that be okay?

> 
>> +
>> +		if (p->in_memstall)
>> +			clear |= TSK_MEMSTALL_RUNNING;
>> +		if (p->in_iowait)
>> +			set |= TSK_IOWAIT;
>> +
>> +		psi_task_change(p, clear, set);
>>  		return;
>> +	}
>>  
>>  	/*
>>  	 * When migrating a task to another CPU, clear all psi
>> -- 
>> 2.56.0.257.gf7497c7d27-goog
>>

-- 
Thanks and Regards,
Prateek


  reply	other threads:[~2026-10-26  5:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 22:04 [PATCH v33 0/7] Sleeping Owner Handling for Proxy Execution (v33) John Stultz
2026-10-23 22:04 ` [PATCH v33 1/7] sched/psi: Preserve sleep-persistent PSI flags on off-CPU sleeping dequeues John Stultz
2026-10-24 11:44   ` Peter Zijlstra
2026-10-26  5:00     ` K Prateek Nayak [this message]
2026-10-26  4:32   ` K Prateek Nayak
2026-10-26  5:16   ` Zhan Xusheng
2026-10-23 22:04 ` [PATCH v33 2/7] sched/core: Use the scheduling context for remote ticks John Stultz
2026-10-24 13:44   ` Kayra Cizmeci
2026-10-23 22:04 ` [PATCH v33 3/7] sched/core: Activate blocked donor when no owner is found John Stultz
2026-10-24  8:33   ` Andrea Righi
2026-10-26  3:02     ` K Prateek Nayak
2026-10-23 22:04 ` [PATCH v33 4/7] sched/proxy: Set TASK_RUNNING when shortcuting return migration John Stultz
2026-10-24  8:36   ` Andrea Righi
2026-10-26  3:09     ` K Prateek Nayak
2026-10-23 22:04 ` [PATCH v33 5/7] sched/proxy: Break cyclic proxy chains by deactivating blocked tasks John Stultz
2026-10-24 21:19   ` Kayra Cizmeci
2026-10-23 22:04 ` [PATCH v33 6/7] sched/proxy: Detect cycles in proxy walks earlier John Stultz
2026-10-24 15:34   ` Kayra Cizmeci
2026-10-23 22:04 ` [PATCH v33 7/7] sched/proxy: Add deactivated (sleeping) owner handling to find_proxy_task() John Stultz
2026-10-24  9:07   ` Andrea Righi
2026-10-26  4:26     ` K Prateek Nayak
2026-10-26  7:40   ` K Prateek Nayak
2026-10-26 19:59   ` Kayra Cizmeci

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=58521a9f-2f05-4176-8b14-96c7b5f0e212@amd.com \
    --to=kprateek.nayak@amd.com \
    --cc=Metin.Kaya@arm.com \
    --cc=arighi@nvidia.com \
    --cc=boqun.feng@gmail.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hupu.gm@gmail.com \
    --cc=joelagnelf@nvidia.com \
    --cc=jstultz@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kernel-team@android.com \
    --cc=kuyo.chang@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=qyousef@layalina.io \
    --cc=rostedt@goodmis.org \
    --cc=sh@gentwo.org \
    --cc=sh_def@163.com \
    --cc=soolaugust@gmail.com \
    --cc=stevensd@google.com \
    --cc=suleiman@google.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=xuewen.yan94@gmail.com \
    --cc=zezeozue@google.com \
    --cc=zhanxusheng@xiaomi.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®