From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: jstultz@google.com
Cc: peterz@infradead.org, hannes@cmpxchg.org, surenb@google.com,
mingo@redhat.com, kprateek.nayak@amd.com, arighi@nvidia.com,
stevensd@google.com, tglx@linutronix.de, juri.lelli@redhat.com,
vincent.guittot@linaro.org, vschneid@redhat.com,
suleiman@google.com, Metin.Kaya@arm.com,
dietmar.eggemann@arm.com, rostedt@goodmis.org,
zezeozue@google.com, longman@redhat.com, boqun.feng@gmail.com,
paulmck@kernel.org, joelagnelf@nvidia.com, qyousef@layalina.io,
xuewen.yan94@gmail.com, kuyo.chang@mediatek.com,
hupu.gm@gmail.com, soolaugust@gmail.com, sh_def@163.com,
sh@gentwo.org, kernel-team@android.com,
linux-kernel@vger.kernel.org, zhanxusheng@xiaomi.com,
Zhan Xusheng <zhanxusheng1024@gmail.com>
Subject: Re: [PATCH v33 1/7] sched/psi: Preserve sleep-persistent PSI flags on off-CPU sleeping dequeues
Date: Mon, 26 Oct 2026 13:16:05 +0800 [thread overview]
Message-ID: <20261026051605.1997313-1-zhanxusheng1024@gmail.com> (raw)
In-Reply-To: <20261023220431.1106611-2-jstultz@google.com>
Hi John,
On Fri, Oct 23, 2026 at 10:04:12PM +0000, John Stultz wrote:
> + if (p->in_memstall)
> + clear |= TSK_MEMSTALL_RUNNING;
> + if (p->in_iowait)
> + set |= TSK_IOWAIT;
> +
> + psi_task_change(p, clear, set);
In this case psi_task_switch() also clears wake_clock when the task going
to sleep is the psi_avgs_work() worker, so the worker doesn't re-arm its
own work. psi_task_change() always passes wake_clock=true, so that check
is lost here.
The worker can get here: psi_avgs_work() takes group->avgs_lock, which
psi_show(), psi_trigger_create() and psi_trigger_destroy() can hold while
sleeping, so it can block on a sleeping owner and be dequeued through
this branch. TSK_ONCPU is already clear by then, since find_proxy_task()
doesn't park a chain that contains curr.
The cost is an extra aggregation period, not the ping-pong described in
psi_task_switch(), but it keeps the averaging clock from shutting off
while idle. Should this branch do the same PF_WQ_WORKER check?
Thanks,
Zhan Xusheng
next prev parent reply other threads:[~2026-10-26 5:16 UTC|newest]
Thread overview: 22+ 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
2026-10-26 4:32 ` K Prateek Nayak
2026-10-26 5:16 ` Zhan Xusheng [this message]
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
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=20261026051605.1997313-1-zhanxusheng1024@gmail.com \
--to=zhanxusheng1024@gmail.com \
--cc=Metin.Kaya@arm.com \
--cc=arighi@nvidia.com \
--cc=boqun.feng@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=hupu.gm@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=kprateek.nayak@amd.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=surenb@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®