From: K Prateek Nayak <kprateek.nayak@amd.com>
To: John Stultz <jstultz@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
<linux-kernel@vger.kernel.org>,
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>,
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: Re: [RFC PATCH 2/3] sched/core: Fix forceidle when lock owner has mismatchd cookie
Date: Thu, 23 Jul 2026 09:31:54 +0530 [thread overview]
Message-ID: <a970144f-df71-4643-ac66-fe37270af774@amd.com> (raw)
In-Reply-To: <CANDhNCqpoJPXuY4S3zS65va7k6VKVJLJSyg4x-62drnWdjiXcg@mail.gmail.com>
Hello Jon,
On 7/23/2026 8:44 AM, John Stultz wrote:
> On Fri, Jul 17, 2026 at 4:17 AM K Prateek Nayak <kprateek.nayak@amd.com> wrote:
>>
>> Move Vasily's fix from 7cd4088f70e0 ("sched/core: Don't proxy-exec
>> unmatched cookie lock owners") into a separate helper and fix the
>> forceidle stats, balance callback queuing when rq is not the one
>> dictating the core cookie.
>>
>> The helper will be extended in subsequent commits to allow for re-pick
>> with cookie from the lock owner if rq is the pick leader.
>>
>> Signed-off-by: K Prateek Nayak <kprateek.nayak@amd.com>
>
> Thanks again for sending these out. I've included these in my full
> proxy-exec-WIP tree and ran into a few build issues with this one.
>
>> ---
>> kernel/sched/core.c | 43 ++++++++++++++++++++++++++++++++++++-------
>> 1 file changed, 36 insertions(+), 7 deletions(-)
>>
>> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> index 31fa6bcee616..ed11410f1416 100644
>> --- a/kernel/sched/core.c
>> +++ b/kernel/sched/core.c
>> @@ -6598,6 +6598,8 @@ __pick_next_task(struct rq *rq, struct rq_flags *rf)
>> BUG(); /* The idle class should always have a runnable task. */
>> }
>>
>> +static void proxy_deactivate(struct rq *rq, struct task_struct *donor);
>> +
>
> So this should probably go in a "#ifdef CONFIG_SCHED_PROXY_EXEC"
> block, or in the !SCHED_PROXY_EXEC case you get defined but not used
> warnings.
>
>
>> @@ -7113,6 +7132,18 @@ pick_next_task(struct rq *rq, struct rq_flags *rf)
>> return __pick_next_task(rq, rf);
>> }
>>
>> +static struct task_struct *
>> +sched_core_swap_pick(struct rq *rq, struct task_struct *next)
>> +{
>> + /*
>> + * Caller should always check !sched_cpu_cookie_match(rq, next)
>> + * which is always false for !CONFIG_SCHED_CORE and execution
>> + * should never reach here.
>> + */
>> + BUG_ON();
>
> This should just be BUG()
>
> I'll fold these fixes up into the patch in my tree, but wanted to give
> you a heads up should you intend to resend these out for review
> sooner.
Thanks a ton for fixing those! Guilty of not testing with
!CONFIG_SCHED_PROXY_EXEC. Will definitely make sure I at least test a
build next time around :-)
I'll wait for your next version and rebase on top of that.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-07-23 4:02 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 ` [RFC PATCH 0/3] sched/core: Allow proxy execution to work with core scheduling K Prateek Nayak
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 [this message]
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=a970144f-df71-4643-ac66-fe37270af774@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®