From: Suleiman Souhlal <suleiman@google.com>
To: linux-kernel@vger.kernel.org
Cc: "Suleiman Souhlal" <suleiman@google.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Ben Segall" <bsegall@google.com>, "Mel Gorman" <mgorman@suse.de>,
"Valentin Schneider" <vschneid@redhat.com>,
"K Prateek Nayak" <kprateek.nayak@amd.com>,
"zhidao su" <soolaugust@gmail.com>,
"John Stultz" <jstultz@google.com>,
"Qais Yousef" <qyousef@google.com>,
ssouhlal@FreeBSD.org
Subject: [RFC PATCH 09/12] futex: Wake up donor in PING futex unlock.
Date: Thu, 17 Sep 2026 04:33:33 +0000 [thread overview]
Message-ID: <20260917043339.2093426-10-suleiman@google.com> (raw)
In-Reply-To: <20260917043339.2093426-1-suleiman@google.com>
Now that PING blockers can act as donors, it makes sense to wake up
the donor instead of the top_waiter when unlocking.
Signed-off-by: Suleiman Souhlal <suleiman@google.com>
---
kernel/futex/ping.c | 56 +++++++++++++++++++++++++++++++++++++--------
1 file changed, 46 insertions(+), 10 deletions(-)
diff --git a/kernel/futex/ping.c b/kernel/futex/ping.c
index 5bf2293bf582..df701b437f16 100644
--- a/kernel/futex/ping.c
+++ b/kernel/futex/ping.c
@@ -478,10 +478,46 @@ int futex_lock_ping(u32 __user *uaddr, unsigned int flags, ktime_t *time,
return ret;
}
+#ifdef CONFIG_SCHED_PROXY_EXEC
+static inline
+struct task_struct *ping_current_proxy_donor(struct futex_pi_state *ping_state)
+{
+ struct task_struct *ret = NULL;
+
+ if (sched_proxy_exec()) {
+ struct task_struct *donor;
+
+ raw_spin_lock(¤t->blocked_lock);
+ donor = current->blocked_donor;
+ if (donor) {
+ void *ping_lock = (void *)&ping_state->ping_mutex;
+
+ raw_spin_lock_nested(&donor->blocked_lock,
+ SINGLE_DEPTH_NESTING);
+ if (__get_task_blocked_on(donor) == ping_lock) {
+ ret = get_task_struct(donor);
+ __clear_task_blocked_on(donor, ping_lock);
+ current->blocked_donor = NULL;
+ }
+ raw_spin_unlock(&donor->blocked_lock);
+ }
+ raw_spin_unlock(¤t->blocked_lock);
+ }
+ return ret;
+}
+#else
+static inline
+struct task_struct *ping_current_proxy_donor(struct futex_pi_state *ping_state)
+{
+ return NULL;
+}
+#endif
+
int futex_unlock_ping(u32 __user *uaddr, unsigned int flags)
{
struct futex_pi_state *ping_state;
u32 new, uval, vpid = task_pid_vnr(current);
+ struct task_struct *next;
union futex_key key = FUTEX_KEY_INIT;
struct futex_q *top_waiter;
DEFINE_WAKE_Q(wake_q);
@@ -528,15 +564,15 @@ int futex_unlock_ping(u32 __user *uaddr, unsigned int flags)
if (!ping_state)
goto out_unlock;
raw_spin_lock_irq(&ping_state->ping_mutex.wait_lock);
- if (ping_state->owner != current) {
- raw_spin_unlock_irq(&ping_state->ping_mutex.wait_lock);
- goto out_unlock;
- }
+
+ next = ping_current_proxy_donor(ping_state);
get_ping_state(ping_state);
/* Leave it queued, it gets unqueued on the lock side */
- get_task_struct(top_waiter->task);
- wake_q_add_safe(&wake_q, top_waiter->task);
- clear_task_blocked_on(top_waiter->task, &ping_state->ping_mutex);
+ if (next == NULL) {
+ next = get_task_struct(top_waiter->task);
+ clear_task_blocked_on(next, &ping_state->ping_mutex);
+ }
+ wake_q_add_safe(&wake_q, next);
spin_unlock(&hb->lock);
/*
@@ -546,10 +582,10 @@ int futex_unlock_ping(u32 __user *uaddr, unsigned int flags)
*/
new = FUTEX_WAITERS;
if (ping_state->handoff) {
- new |= task_pid_vnr(top_waiter->task);
+ new |= task_pid_vnr(next);
ping_state->handoff = 0;
ping_state->pickup = 1;
- WRITE_ONCE(ping_state->ping_mutex.owner, top_waiter->task);
+ WRITE_ONCE(ping_state->ping_mutex.owner, next);
} else
WRITE_ONCE(ping_state->ping_mutex.owner, NULL);
ret = lock_pi_update_atomic(uaddr, uval, new);
@@ -568,7 +604,7 @@ int futex_unlock_ping(u32 __user *uaddr, unsigned int flags)
}
}
- ping_state_update_owner(ping_state, top_waiter->task);
+ ping_state_update_owner(ping_state, next);
raw_spin_unlock_irq_wake(&ping_state->ping_mutex.wait_lock, &wake_q);
put_ping_state(ping_state);
return 0;
--
2.55.0.1082.g2b9226bbc0-goog
next prev parent reply other threads:[~2026-09-17 4:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 4:33 [RFC PATCH 00/12] FUTEX_PING: A stealable futex using Proxy Execution Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 01/12] sched: Abstract task_struct->blocked_on by locking primitive Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 02/12] futex: Switch PI futex to use p->pi_futex_lock instead of p->pi_lock Suleiman Souhlal
2026-09-17 15:38 ` Peter Zijlstra
2026-09-17 4:33 ` [RFC PATCH 03/12] futex: Add "ping" parameter to pi_state management functions and export them Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 04/12] futex: Introduce stealable PI futex, FUTEX_*_PING Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 05/12] futex: Implement exit_ping_state_list() Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 06/12] futex: Address aborting from futex_lock_ping() while owning ping_state Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 07/12] futex: Make FUTEX_*_PING use Proxy Execution Suleiman Souhlal
2026-09-17 13:18 ` Jihan LIN
2026-09-17 14:39 ` K Prateek Nayak
2026-09-17 15:36 ` Peter Zijlstra
2026-09-17 4:33 ` [RFC PATCH 08/12] futex: Implement PING futex handoff Suleiman Souhlal
2026-09-17 4:33 ` Suleiman Souhlal [this message]
2026-09-17 4:33 ` [RFC PATCH 10/12] futex: Optimistic spinning for PING futexes Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 11/12] futex: Allow userspace stealing " Suleiman Souhlal
2026-09-17 4:33 ` [RFC PATCH 12/12] tools/testing/futex: Add ping_bench, a tool for benchmarking futexes Suleiman Souhlal
2026-09-17 8:58 ` [RFC PATCH 00/12] FUTEX_PING: A stealable futex using Proxy Execution Peter Zijlstra
2026-09-17 17:53 ` John Stultz
2026-09-17 18:51 ` Steven Rostedt
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=20260917043339.2093426-10-suleiman@google.com \
--to=suleiman@google.com \
--cc=andrealmeid@igalia.com \
--cc=bsegall@google.com \
--cc=dave@stgolabs.net \
--cc=dietmar.eggemann@arm.com \
--cc=dvhart@infradead.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qyousef@google.com \
--cc=rostedt@goodmis.org \
--cc=soolaugust@gmail.com \
--cc=ssouhlal@FreeBSD.org \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®