From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-6.16] sched_ext: Remove cpu.weight / cpu.idle unimplemented warnings
Date: Tue, 8 Apr 2025 08:01:29 -1000 [thread overview]
Message-ID: <Z_Vkede_M_VxPl08@slm.duckdns.org> (raw)
In-Reply-To: <Z_VjE_d9A6wRfZlx@slm.duckdns.org>
On Tue, Apr 08, 2025 at 07:55:31AM -1000, Tejun Heo wrote:
> On Mon, Apr 07, 2025 at 01:20:04PM -1000, Tejun Heo wrote:
> > sched_ext generates warnings when cpu.weight / cpu.idle are set to
> > non-default values if the BPF scheduler doesn't implement weight support.
> > These warnings don't provide much value while adding constant annoyance. A
> > BPF scheduler may not implement any particular behavior and there's nothing
> > particularly special about missing cgroup weight support. Drop the warnings.
> >
> > Signed-off-by: Tejun Heo <tj@kernel.org>
>
> Applied to sched_ext/for-6.16.
Strike that. Applied to for-6.15-fixes instead. Better to get rid of it
sooner than later.
Thanks.
--
tejun
prev parent reply other threads:[~2025-04-08 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 23:20 [PATCH sched_ext/for-6.16] sched_ext: Remove cpu.weight / cpu.idle unimplemented warnings Tejun Heo
2025-04-08 1:23 ` Changwoo Min
2025-04-08 7:58 ` Andrea Righi
2025-04-08 18:12 ` [PATCH sched_ext/for-6.15-fixes] sched_ext: Mark SCX_OPS_HAS_CGROUP_WEIGHT for deprecation Tejun Heo
2025-04-08 18:28 ` Andrea Righi
2025-04-08 18:29 ` Tejun Heo
2025-04-08 18:31 ` [PATCH v2 " Tejun Heo
2025-04-08 18:41 ` Andrea Righi
2025-04-08 18:54 ` Tejun Heo
2025-04-08 17:55 ` [PATCH sched_ext/for-6.16] sched_ext: Remove cpu.weight / cpu.idle unimplemented warnings Tejun Heo
2025-04-08 18:01 ` Tejun Heo [this message]
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=Z_Vkede_M_VxPl08@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.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