From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
John Stultz <jstultz@google.com>, <linux-kernel@vger.kernel.org>
Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
Qais Yousef <qyousef@layalina.io>,
Zimuzo Ezeozue <zezeozue@google.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Metin Kaya <Metin.Kaya@arm.com>,
Xuewen Yan <xuewen.yan94@gmail.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
Suleiman Souhlal <suleiman@google.com>,
kuyo chang <kuyo.chang@mediatek.com>, hupu <hupu.gm@gmail.com>,
Vasily Gorbik <gor@linux.ibm.com>, <kernel-team@android.com>
Subject: [RFC PATCH 0/3] sched/core: Allow proxy execution to work with core scheduling
Date: Fri, 17 Jul 2026 11:15:58 +0000 [thread overview]
Message-ID: <20260717111601.6017-1-kprateek.nayak@amd.com> (raw)
In-Reply-To: <CANDhNCoVw1Z0RGoB34f-NHF=XK_AvcGXr2e3ctjd4FZa0pkWSg@mail.gmail.com>
Proxy execution runs the lock owner in place of blocked donor returned
by pick_next_task() but the lock owner can have a different core-cookie
compared to the blocked donor and simply running the lock owner under
those circumstances breaks the guarantees of core scheduling.
Allow proxy execution to exist alognside core scheduling by forcing a
re-pick once the blocked_on chain is found to be stable in __schedule()
and then swapping the rq->core_pick with the lock owner allowing the
execution context to dictate the core-cookie.
Lightly tested with John's priority-inversion-demo [1] patched with
"coresched new -t pid --" and the plotted chart seems to suggest proxy
is working [2]. Your mileage may vary :-)
I'll update the thread if I find any nasty bugs over the weekend run.
Patches are prepared on top of:
https://github.com/johnstultz-work/linux-dev.git proxy-exec-v30-7.2-rc1
at commit abb09adc985b ("HACK: scx: Add scx_prio_inversion test
scheduler") with commit 93bd6418a6ea ("sched/core: Skip
put_prev_task/set_next_task re-entry for sched_ext donors") reverted on
top to make !EXT builds happy.
This is essentially a formal version of [3] broken down to be slightly
more readable. Comments and feedback are always appreciated!
References
==========
[1] https://github.com/johnstultz-work/priority-inversion-demo/
[2] https://imgur.com/NsgWqRx
[3] https://lore.kernel.org/lkml/9ceb2af0-33c6-40ca-b855-5167a9c5ae0f@amd.com/
--
K Prateek Nayak (3):
sched/core: Track the core-wide pick leader
sched/core: Fix forceidle when lock owner has mismatchd cookie
sched/core: Swap to lock owner for core-wide pick on core-cookie
mismatch
kernel/sched/core.c | 129 ++++++++++++++++++++++++++++++++++++++-----
kernel/sched/sched.h | 4 ++
2 files changed, 119 insertions(+), 14 deletions(-)
--
2.43.0
next prev parent reply other threads:[~2026-07-17 11:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 21:45 [PATCH v30 0/7] Sleeping Owner Handling for Proxy Execution (v30) John Stultz
2026-07-01 21:45 ` [PATCH v30 1/7] sched/core: Don't steal a proxy-exec donor John Stultz
2026-07-01 21:45 ` [PATCH v30 2/7] sched/core: Avoid migrating blocked_on tasks John Stultz
2026-07-01 21:45 ` [PATCH v30 3/7] sched/core: Don't proxy-exec unmatched cookie lock owners John Stultz
2026-07-02 5:13 ` K Prateek Nayak
2026-07-02 9:14 ` Peter Zijlstra
2026-07-08 5:00 ` John Stultz
2026-07-10 3:13 ` K Prateek Nayak
2026-07-10 3:32 ` John Stultz
2026-07-17 11:15 ` K Prateek Nayak [this message]
2026-07-17 11:15 ` [RFC PATCH 1/3] sched/core: Track the core-wide pick leader K Prateek Nayak
2026-07-17 11:16 ` [RFC PATCH 2/3] sched/core: Fix forceidle when lock owner has mismatchd cookie K Prateek Nayak
2026-07-23 3:14 ` John Stultz
2026-07-23 4:01 ` K Prateek Nayak
2026-07-17 11:16 ` [RFC PATCH 3/3] sched/core: Swap to lock owner for core-wide pick on core-cookie mismatch K Prateek Nayak
2026-07-18 6:22 ` K Prateek Nayak
2026-07-18 7:01 ` [RFC PATCH 0/3] sched/core: Allow proxy execution to work with core scheduling John Stultz
2026-07-01 21:45 ` [PATCH v30 4/7] sched: Switch rq->next_class in proxy_reset_donor() John Stultz
2026-07-01 21:46 ` [PATCH v30 5/7] sched: Break out core of attach_tasks() helper into sched.h John Stultz
2026-07-01 21:46 ` [PATCH v30 6/7] sched: Migrate whole chain in proxy_migrate_task() John Stultz
2026-07-01 21:46 ` [PATCH v30 7/7] sched: Add deactivated (sleeping) owner handling to find_proxy_task() John Stultz
2026-07-03 3:06 ` K Prateek Nayak
2026-07-08 4:34 ` John Stultz
2026-07-10 4:03 ` K Prateek Nayak
2026-07-10 4:56 ` John Stultz
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=20260717111601.6017-1-kprateek.nayak@amd.com \
--to=kprateek.nayak@amd.com \
--cc=Metin.Kaya@arm.com \
--cc=boqun.feng@gmail.com \
--cc=bsegall@google.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=gor@linux.ibm.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=suleiman@google.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.com \
--cc=zezeozue@google.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®