From: K Prateek Nayak <kprateek.nayak@amd.com>
To: John Stultz <jstultz@google.com>, LKML <linux-kernel@vger.kernel.org>
Cc: 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>,
Mel Gorman <mgorman@suse.de>, 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: [RESEND][PATCH v21 1/6] locking: Add task::blocked_lock to serialize blocked_on state
Date: Fri, 12 Sep 2025 11:20:22 +0530 [thread overview]
Message-ID: <a6c0b576-393d-4283-86ab-5c88c22ebdc3@amd.com> (raw)
In-Reply-To: <20250904002201.971268-2-jstultz@google.com>
Hello John,
On 9/4/2025 5:51 AM, John Stultz wrote:
> @@ -693,25 +697,30 @@ __mutex_lock_common(struct mutex *lock, unsigned int state, unsigned int subclas
> break;
>
> if (first) {
> - trace_contention_begin(lock, LCB_F_MUTEX | LCB_F_SPIN);
> + bool opt_acquired;
> +
> /*
> * mutex_optimistic_spin() can call schedule(), so
> - * clear blocked on so we don't become unselectable
> + * we need to release these locks before calling it,
> + * and clear blocked on so we don't become unselectable
> * to run.
> */
> - clear_task_blocked_on(current, lock);
> - if (mutex_optimistic_spin(lock, ww_ctx, &waiter))
> + __clear_task_blocked_on(current, lock);
> + raw_spin_unlock(¤t->blocked_lock);
> + raw_spin_unlock_irqrestore(&lock->wait_lock, flags);
> + trace_contention_begin(lock, LCB_F_MUTEX | LCB_F_SPIN);
> + opt_acquired = mutex_optimistic_spin(lock, ww_ctx, &waiter);
> + raw_spin_lock_irqsave(&lock->wait_lock, flags);
> + raw_spin_lock(¤t->blocked_lock);
> + __set_task_blocked_on(current, lock);
> + if (opt_acquired)
> break;
nit. Is there any reason for setting the blocked state before the break
other than for symmetry? The blocked_lock is held and we'll soon clear
it after the break anyways so does it have any other subtle purpose?
Also super silly but that above block is too dense. Can we add some
spaces in between, groping the relevant ops, to make it easier on the
eyes :)
Apart from those nit picks, I don't see anything out of the place.
Feel free to include:
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
I'm still lagging behind on testing (Sorry about that!) but I should
have the results for this by Monday.
--
Thanks and Regards,
Prateek
> - set_task_blocked_on(current, lock);
> trace_contention_begin(lock, LCB_F_MUTEX);
> }
> -
> - raw_spin_lock_irqsave(&lock->wait_lock, flags);
> }
> - raw_spin_lock_irqsave(&lock->wait_lock, flags);
> -acquired:
> __clear_task_blocked_on(current, lock);
> __set_current_state(TASK_RUNNING);
> + raw_spin_unlock(¤t->blocked_lock);
>
> if (ww_ctx) {
> /*
next prev parent reply other threads:[~2025-09-12 5:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 0:21 [RESEND][PATCH v21 0/6] Donor Migration for Proxy Execution (v21) John Stultz
2025-09-04 0:21 ` [RESEND][PATCH v21 1/6] locking: Add task::blocked_lock to serialize blocked_on state John Stultz
2025-09-12 5:50 ` K Prateek Nayak [this message]
2025-09-18 19:58 ` John Stultz
2025-09-04 0:21 ` [RESEND][PATCH v21 2/6] sched/locking: Add blocked_on_state to provide necessary tri-state for proxy return-migration John Stultz
2025-09-15 8:05 ` K Prateek Nayak
2025-09-18 22:57 ` John Stultz
2025-09-19 3:27 ` K Prateek Nayak
2025-09-23 23:34 ` John Stultz
2025-09-15 9:03 ` K Prateek Nayak
2025-09-18 23:07 ` John Stultz
2025-09-19 3:38 ` K Prateek Nayak
2025-09-04 0:21 ` [RESEND][PATCH v21 3/6] sched: Add logic to zap balance callbacks if we pick again John Stultz
2025-09-15 8:31 ` K Prateek Nayak
2025-09-19 18:34 ` John Stultz
2025-09-04 0:21 ` [RESEND][PATCH v21 4/6] sched: Handle blocked-waiter migration (and return migration) John Stultz
2025-09-15 10:06 ` K Prateek Nayak
2025-09-20 2:38 ` John Stultz
2025-09-22 4:14 ` K Prateek Nayak
2025-09-04 0:21 ` [RESEND][PATCH v21 5/6] sched: Add blocked_donor link to task for smarter mutex handoffs John Stultz
2025-09-04 0:21 ` [RESEND][PATCH v21 6/6] sched: Migrate whole chain in proxy_migrate_task() John Stultz
2025-09-11 13:59 ` [RESEND][PATCH v21 0/6] Donor Migration for Proxy Execution (v21) Juri Lelli
2025-09-11 23:21 ` John Stultz
2025-09-12 8:14 ` Juri Lelli
2025-09-16 3:19 ` K Prateek Nayak
2025-09-16 4:57 ` 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=a6c0b576-393d-4283-86ab-5c88c22ebdc3@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=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=mgorman@suse.de \
--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®