mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [PATCH] sched/core: Account PSI IRQ time to the execution context
@ 2026-09-18 13:29 Zhan Xusheng
  2026-09-18 17:34 ` Hui Su
  0 siblings, 1 reply; 2+ messages in thread
From: Zhan Xusheng @ 2026-09-18 13:29 UTC (permalink / raw)
  To: peterz, mingo
  Cc: hannes, surenb, jstultz, connoro, metin.kaya, sh_def, juri.lelli,
	vincent.guittot, dietmar.eggemann, rostedt, bsegall, mgorman,
	vschneid, kprateek.nayak, linux-kernel, zhanxusheng

psi_account_irqtime() has two callers which share rq->psi_irq_time, and
they disagree about the context: __schedule() passes the outgoing rq->curr,
sched_tick() passes rq->donor.  Under proxy execution the donor is blocked
on a mutex while rq->curr burns the CPU.

The tick charges PSI_IRQ_FULL to the donor's cgroup and advances the
timestamp, so the call from __schedule() then finds delta <= 0 and charges
nothing.  The delta is not counted twice, it lands on the wrong cgroup.

Pass rq->curr, which is what the call read before commit af0c8b2bf67b
("sched: Split scheduler and execution contexts") renamed curr to donor
across sched_tick().  Without CONFIG_SCHED_PROXY_EXEC the two rq members
are a union, so this only changes anything where that option is set, and
it depends on EXPERT.

Fixes: af0c8b2bf67b ("sched: Split scheduler and execution contexts")
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
---
Built and booted on x86_64 with CONFIG_SCHED_PROXY_EXEC=y, PSI and
IRQ_TIME_ACCOUNTING enabled, under x86_debug.config and panic_on_warn.
I did not construct a case where donor and curr differ.
 kernel/sched/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 7885ff76e69f..2b48ae0ab372 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -5791,7 +5791,7 @@ void sched_tick(void)
 	curr = rq->curr;
 	donor = rq->donor;
 
-	psi_account_irqtime(rq, donor, NULL);
+	psi_account_irqtime(rq, curr, NULL);
 
 	update_rq_clock(rq);
 	hw_pressure = arch_scale_hw_pressure(cpu_of(rq));

base-commit: 5dd1818b15d98d4a20806cd00b1b40320b06004f
-- 
2.43.0


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] sched/core: Account PSI IRQ time to the execution context
  2026-09-18 13:29 [PATCH] sched/core: Account PSI IRQ time to the execution context Zhan Xusheng
@ 2026-09-18 17:34 ` Hui Su
  0 siblings, 0 replies; 2+ messages in thread
From: Hui Su @ 2026-09-18 17:34 UTC (permalink / raw)
  To: Zhan Xusheng
  Cc: Peter Zijlstra, Ingo Molnar, hannes, surenb, jstultz, connoro,
	metin.kaya, sh_def, juri.lelli, vincent.guittot,
	dietmar.eggemann, rostedt, bsegall, mgorman, vschneid,
	kprateek.nayak, linux-kernel, zhanxusheng

> I did not construct a case where donor and curr differ.

I tested two proxy-execution processes in separate cgroup v2 cgroups.
The owner held a CPU0 mutex for 20s; a SCHED_FIFO donor blocked on it.
On x86_64 QEMU (4 vCPUs, 2 GiB), with PSI and IRQ time accounting enabled,
the irq.pressure total deltas (us) were:
  unpatched: owner 22,053, donor 401,127
  patched:   owner 552,740, donor 31,566
Both runs completed successfully, and attribution moved to execution context.
This exercises the donor != curr case missing from the original test.

Tested-by: Hui Su <sh_def@163.com>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-09-18 17:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-18 13:29 [PATCH] sched/core: Account PSI IRQ time to the execution context Zhan Xusheng
2026-09-18 17:34 ` Hui Su

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®