From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, David Vernet <void@manifault.com>,
sched-ext@meta.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>
Subject: [GIT PULL] sched_ext: Fixes for v6.12-rc2
Date: Tue, 8 Oct 2024 09:42:16 -1000 [thread overview]
Message-ID: <ZwWLGKG4fsUYQyub@slm.duckdns.org> (raw)
The following changes since commit 95b873693a0841e02b812e693296a884362fdd51:
sched_ext: Remove redundant p->nr_cpus_allowed checker (2024-09-27 10:23:45 -1000)
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.12-rc2-fixes
for you to fetch changes up to e0ed52154e866a1e9e9b97ded50b164698f0a222:
sched_ext: Documentation: Update instructions for running example schedulers (2024-10-08 08:49:18 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v6.12-rc2
- ops.enqueue() didn't have a way to tell whether select_task_rq_scx() and
thus ops.select() were skipped. Some schedulers were incorrectly using
SCX_ENQ_WAKEUP. Add SCX_ENQ_CPU_SELECTED and fix scx_qmap using it.
- Remove a spurious WARN_ON_ONCE() in scx_cgroup_exit().
- Fix error information clobbering during load.
- Add missing __weak markers to BPF helper declarations.
- Doc update.
----------------------------------------------------------------
Devaansh-Kumar (1):
sched_ext: Documentation: Update instructions for running example schedulers
Tejun Heo (5):
sched_ext: Improve error reporting during loading
sched_ext: scx_cgroup_exit() may be called without successful scx_cgroup_init()
sched/core: Make select_task_rq() take the pointer to wake_flags instead of value
sched/core: Add ENQUEUE_RQ_SELECTED to indicate whether ->select_task_rq() was called
sched_ext, scx_qmap: Add and use SCX_ENQ_CPU_SELECTED
Vishal Chourasia (1):
sched_ext: Add __weak markers to BPF helper function decalarations
Documentation/scheduler/sched-ext.rst | 2 +-
kernel/sched/core.c | 21 ++++++++++++++-------
kernel/sched/ext.c | 32 ++++++++++++++++++++------------
kernel/sched/sched.h | 3 +++
tools/sched_ext/include/scx/common.bpf.h | 6 +++---
tools/sched_ext/scx_qmap.bpf.c | 4 ++--
6 files changed, 43 insertions(+), 25 deletions(-)
--
tejun
next reply other threads:[~2024-10-08 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 19:42 Tejun Heo [this message]
2024-10-08 20:16 ` 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=ZwWLGKG4fsUYQyub@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sched-ext@meta.com \
--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
all inboxes | Powered by JetHome®