From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Subject: [GIT PULL] sched_ext: Fixes for v6.15-rc3
Date: Mon, 21 Apr 2025 09:37:15 -1000 [thread overview]
Message-ID: <aAaea_h3ORZGmkxp@slm.duckdns.org> (raw)
The following changes since commit 4a1d8ababde685a77fd4fd61e58f973cbdf29f8c:
Merge tag 'riscv-for-linus-6.15-mw1' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux (2025-04-04 09:49:17 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/ tags/sched_ext-for-6.15-rc3-fixes
for you to fetch changes up to bc08b15b54b8aadbc8a8f413271c07a3f4bead87:
sched_ext: Mark SCX_OPS_HAS_CGROUP_WEIGHT for deprecation (2025-04-08 08:53:52 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v6.15-rc3
- Use kvzalloc() so that large exit_dump buffer allocations don't fail
easily.
- Remove cpu.weight / cpu.idle unimplemented warnings which are more
annoying than helpful. This makes SCX_OPS_HAS_CGROUP_WEIGHT unnecessary.
Mark it for deprecation.
----------------------------------------------------------------
Breno Leitao (1):
sched_ext: Use kvzalloc for large exit_dump allocation
Tejun Heo (2):
sched_ext: Remove cpu.weight / cpu.idle unimplemented warnings
sched_ext: Mark SCX_OPS_HAS_CGROUP_WEIGHT for deprecation
kernel/sched/ext.c | 50 ++++++----------------------------------
tools/sched_ext/scx_flatcg.bpf.c | 2 +-
2 files changed, 8 insertions(+), 44 deletions(-)
--
tejun
next reply other threads:[~2025-04-21 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 19:37 Tejun Heo [this message]
2025-04-22 2:25 ` [GIT PULL] sched_ext: Fixes for v6.15-rc3 pr-tracker-bot
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=aAaea_h3ORZGmkxp@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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