diff options
| author | Breno Leitao <leitao@debian.org> | 2026-06-24 02:27:43 -0700 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-06-24 08:54:28 -1000 |
| commit | 4cd5de72b6f8951cef6b45c177a582824bc13d46 (patch) | |
| tree | 20e9a84a89efb8eafd47b25dbecaba33193614bc /Documentation/gpu/intel-display/git@git.tavy.me:linux.git | |
| parent | f0e6f20cb52b14c2c441f04e21cef0c95d498cac (diff) | |
sched_ext: Avoid flooding the log with deprecation warnings
The deprecation notices for direct p->scx.slice/dsq_vtime writes and for
ops->cpu_acquire/release() use plain pr_warn(), so they repeat on every
scheduler (re)load and can flood the kernel log.
The slice/dsq_vtime notice is the worst offender: it is emitted from the
BPF verifier's btf_struct_access callback, which is re-evaluated as the
verifier explores program paths, so a single scheduler load can print it
many times -- hundreds of lines on some hosts, dozens within the same
second.
Switch both notices to pr_warn_ratelimited() so each deprecation is still
reported but bursts no longer spam the log, and add the missing newline
to the slice/dsq_vtime message.
Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'Documentation/gpu/intel-display/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
