diff options
| author |   Andrea Righi <arighi@nvidia.com> | 2025-04-23 23:02:05 +0200 |
|---|---|---|
| committer |   Tejun Heo <tj@kernel.org> | 2025-04-23 13:34:32 -1000 |
| commit | 069ac9e161eb9d5bfd5a4a5bf016522353226a51 (patch) | |
| tree | d701fab2064903f77cd3388222c467ccc10b95b5 /scripts/lib/kdoc/kdoc_re.py | |
| parent | Merge branch 'for-6.15-fixes' into for-6.16 (diff) | |
| download | wireguard-linux-069ac9e161eb9d5bfd5a4a5bf016522353226a51.tar.xz wireguard-linux-069ac9e161eb9d5bfd5a4a5bf016522353226a51.zip | |
sched_ext: Clarify CPU context for running/stopping callbacks
The ops.running() and ops.stopping() callbacks can be invoked from a CPU
other than the one the task is assigned to, particularly when a task
property is changed, as both scx_next_task_scx() and dequeue_task_scx() may
run on CPUs different from the task's target CPU.
This behavior can lead to confusion or incorrect assumptions if not
properly clarified, potentially resulting in bugs (see [1]).
Therefore, update the documentation to clarify this aspect and advise
users to use scx_bpf_task_cpu() to determine the actual CPU the task
will run on or was running on.
[1] https://github.com/sched-ext/scx/pull/1728
Cc: Jake Hillion <jake@hillion.co.uk>
Signed-off-by: Andrea Righi <arighi@nvidia.com>
Acked-by: Changwoo Min <changwoo@igalia.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_re.py')
0 files changed, 0 insertions, 0 deletions