From: Andrea Righi <arighi@nvidia.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: Breno Leitao <leitao@debian.org>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
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>,
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>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] sched_ext: Print deprecation warnings only once
Date: Tue, 23 Jun 2026 17:53:33 +0200 [thread overview]
Message-ID: <ajqr_biPOFkugwIx@gpd4> (raw)
In-Reply-To: <43d5e4e0-eddb-4a7a-87df-180b9048a038@arm.com>
Hi Breno and Christian,
On Tue, Jun 23, 2026 at 04:45:55PM +0100, Christian Loehle wrote:
> On 6/23/26 15:38, Breno Leitao wrote:
> > 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 flood the kernel log.
> > > The slice/dsq_vtime notice is emitted from the BPF verifier's
> > btf_struct_access callback, which runs once per write access and is
> > re-evaluated as the verifier explores paths, so loading a single
> > scheduler can print it several times. The cpu_acquire/release notice is
> > printed on every scheduler enable.
> >
> > Switch both to pr_warn_once() so each deprecation is reported a single
> > time, and add the missing newline to the slice/dsq_vtime message.
>
> I guess this should be warned for once per BPF scheduler like
> sch->warned_deprecated_rq
Yeah, I agree. The thing is that we can load multiple different BPF schedulers,
and we'd want to get these messages for each of them. So ideally we need
something like sch->warned_deprecated_rq.
Thanks,
-Andrea
>
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> > kernel/sched/ext/ext.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> > index 691d53fe0f648..708eb9024cb25 100644
> > --- a/kernel/sched/ext/ext.c
> > +++ b/kernel/sched/ext/ext.c
> > @@ -6988,7 +6988,7 @@ static int validate_ops(struct scx_sched *sch, const struct sched_ext_ops *ops)
> > * run past the BPF allocation. Skip for cid-form.
> > */
> > if (!sch->is_cid_type && (ops->cpu_acquire || ops->cpu_release))
> > - pr_warn("ops->cpu_acquire/release() are deprecated, use sched_switch TP instead\n");
> > + pr_warn_once("ops->cpu_acquire/release() are deprecated, use sched_switch TP instead\n");
> >
> > /*
> > * Sub-scheduler support is tied to the cid-form struct_ops. A sub-sched
> > @@ -7806,7 +7806,7 @@ static int bpf_scx_btf_struct_access(struct bpf_verifier_log *log,
> > off + size <= offsetofend(struct task_struct, scx.slice)) ||
> > (off >= offsetof(struct task_struct, scx.dsq_vtime) &&
> > off + size <= offsetofend(struct task_struct, scx.dsq_vtime))) {
> > - pr_warn("sched_ext: Writing directly to p->scx.slice/dsq_vtime is deprecated, use scx_bpf_task_set_slice/dsq_vtime()");
> > + pr_warn_once("sched_ext: Writing directly to p->scx.slice/dsq_vtime is deprecated, use scx_bpf_task_set_slice/dsq_vtime()\n");
> > return SCALAR_VALUE;
> > }
> >
> >
> > ---
> > base-commit: 4e5dfb7c84012007c3c7061126491bbc92d71bf1
> > change-id: 20260623-scx_warning-0df49c442afb
> >
> > Best regards,
>
next prev parent reply other threads:[~2026-06-23 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 14:38 [PATCH] sched_ext: Print deprecation warnings only once Breno Leitao
2026-06-23 15:45 ` Christian Loehle
2026-06-23 15:53 ` Andrea Righi [this message]
2026-06-23 16:45 ` Breno Leitao
2026-06-23 17:33 ` Andrea Righi
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=ajqr_biPOFkugwIx@gpd4 \
--to=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=kprateek.nayak@amd.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.