diff options
| author | Shubhang Kaushik (Ampere) <sh@gentwo.org> | 2026-09-22 14:57:05 -0700 |
|---|---|---|
| committer | Ingo Molnar <mingo@kernel.org> | 2026-09-25 20:32:31 +0200 |
| commit | 627ea30aca3b309af40cdd07a35eb1027ba4a0bc (patch) | |
| tree | 46d0e58bd2f1bf0816f77ef49ec8164daf36c3a9 /tools/lib/python/kdoc/python_version.py | |
| parent | d2e0100827578641df2f85546bdb57bb1d8ff55b (diff) | |
sched/wait: Clarify WF_SYNC wakeup semantics
The synchronous waitqueue wakeup comments currently state that a
synchronous wakee will not be migrated to another CPU. This is not
guaranteed by the scheduler wakeup path.
WF_SYNC is an advisory hint that the caller expects the waker to
schedule away soon. Scheduler classes may use it for placement or
preemption, but callers must not rely on it to prevent migration,
preserve CPU locality, or make the wakee run next.
Keep this contract next to the flag definition, remove the stale
waitqueue wording, and make the locked helper refer to the unlocked
variant.
Signed-off-by: Shubhang Kaushik (Ampere) <sh@gentwo.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://patch.msgid.link/20260922-sched-wf-sync-doc-v3-1-23ebe9e27bef@gentwo.org
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions