From: Peter Zijlstra <peterz@infradead.org>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>
Cc: Zhan Xusheng <zhanxusheng@xiaomi.com>,
mingo@redhat.com, hannes@cmpxchg.org, surenb@google.com,
jstultz@google.com, connoro@google.com, metin.kaya@arm.com,
sh_def@163.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, kprateek.nayak@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/core: Account PSI IRQ time to the execution context
Date: Tue, 22 Sep 2026 11:49:44 +0200 [thread overview]
Message-ID: <20260922094944.GN1837346@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260922091532.2504886-1-zhanxusheng@xiaomi.com>
On Tue, Sep 22, 2026 at 05:15:31PM +0800, Zhan Xusheng wrote:
> On Tue, Sep 22, 2026 at 10:17:06AM +0200, Peter Zijlstra wrote:
> > Does not in fact apply. There is no curr in sched_tick anymore.
>
> It needs commit f5741d2b3451 ("sched/core: Call wq_worker_tick() for the
> execution context"), which added that local. That is in sched/urgent and
> master, not in sched/core, and the patch applies cleanly to the first two.
>
> If you want it on sched/core instead, I will resend using rq->curr at the
> call site.
Hmm, I thought I was on tip/master which should have /urgent on, but let
me try again. Perhaps I fat-fingered something.
next prev parent reply other threads:[~2026-09-22 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 13:29 Zhan Xusheng
2026-09-18 17:34 ` Hui Su
2026-09-22 3:30 ` John Stultz
2026-09-22 8:17 ` Peter Zijlstra
2026-09-22 9:15 ` Zhan Xusheng
2026-09-22 9:49 ` Peter Zijlstra [this message]
2026-09-22 9:51 ` Peter Zijlstra
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=20260922094944.GN1837346@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=connoro@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=metin.kaya@arm.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sh_def@163.com \
--cc=surenb@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=zhanxusheng1024@gmail.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®