From: K Prateek Nayak <kprateek.nayak@amd.com>
To: John Stultz <jstultz@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Joel Fernandes <joelagnelf@nvidia.com>,
Qais Yousef <qyousef@layalina.io>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Valentin Schneider <vschneid@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
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>,
<kernel-team@android.com>
Subject: Re: [PATCH v30 3/7] sched/core: Don't proxy-exec unmatched cookie lock owners
Date: Fri, 10 Jul 2026 08:43:49 +0530 [thread overview]
Message-ID: <d819b06f-10e1-4695-a005-1aa5f98fd6a3@amd.com> (raw)
In-Reply-To: <CANDhNCrF0=xVqJLfHW_7o2yWPGgsey_cYaBQdq_=Y0K2AAbVxw@mail.gmail.com>
Hello John,
On 7/8/2026 10:30 AM, John Stultz wrote:
>> https://lore.kernel.org/lkml/9ceb2af0-33c6-40ca-b855-5167a9c5ae0f@amd.com/
>>
>
> Oh! Very interesting! My apologies for somehow having overlooked this mail!
>
>
>> I can streamline that more on top of current tip to do it all in
>> pick_next_task() but the bigger question is, is it worth all the
>> complexity?
>>
>> John, Peter, what do you think?
>>
>> [..snip..]
>>
>>> @@ -7004,6 +7004,14 @@ find_proxy_task(struct rq *rq, struct task_struct *donor, struct rq_flags *rf)
>>> owner->blocked_donor = p;
>>> }
>>> WARN_ON_ONCE(owner && !owner->on_rq);
>>> +
>>> + if (owner && !sched_cpu_cookie_match(rq, owner)) {
>>> + if (curr_in_chain)
>>> + return proxy_resched_idle(rq);
>>> + p = donor; /* Deactivate the donor, not the runnable owner */
>>> + clear_task_blocked_on(p, NULL);
>>> + goto deactivate;
>>> + }
>>
>> Otherwise, this is acceptable if we don't want to touch core-sched
>> bits juts yet.
>
> Vasily's patch I think is a reasonable short-term solution just to
> avoid breaking core-scheduling with proxy, but it's not a great
> solution as it just disables proxy in the problematic cases.
Ack! We can add this in and work on the CORE_SCHED bits before we drop
the EXPERT dependency perhaps?
I doubt if anyone would notice if PROXY is missing with CORE_SCHED but
if and when we plan to retire RT_MUTEXES in favor of PROXY_EXEC, we
should have it in for correctness.
> So I'm very interested in your proposal, as I was thinking I'd have to
> pick folks' brains at LPC to figure out a better approach. But it
> might be worth taking Vasily's patch while yours gets polished and
> tested?
> I'll try pulling your change in to test with my full tree.
I'll send a clean series out by early next week after some more testing
on top of your WIP branch.
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2026-07-10 3:14 UTC|newest]
Thread overview: 21+ 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 [this message]
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-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-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=d819b06f-10e1-4695-a005-1aa5f98fd6a3@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