From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
sched-ext@meta.com, David Vernet <void@manifault.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT PULL] sched_ext: Fixes for v6.12-rc1
Date: Mon, 23 Sep 2024 07:18:48 -1000 [thread overview]
Message-ID: <ZvGi-Ciqmy8U5g_j@slm.duckdns.org> (raw)
In-Reply-To: <ZvGfmIJt-5gg9EwU@slm.duckdns.org>
Forgot to cc Peter and Ingo for the fixes that touch sched core. Cc'ing and
quoting whole body.
On Mon, Sep 23, 2024 at 07:04:24AM -1000, Tejun Heo wrote:
> The following changes since commit 88264981f2082248e892a706b2c5004650faac54:
>
> Merge tag 'sched_ext-for-6.12' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext (2024-09-21 09:44:57 -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.12-rc1-fixes
>
> for you to fetch changes up to 431844b65f4c1b988ccd886f2ed29c138f7bb262:
>
> sched_ext: Provide a sysfs enable_seq counter (2024-09-23 06:53:02 -1000)
>
> ----------------------------------------------------------------
> sched_ext: Fixes for v6.12-rc1
>
> - Three build fixes.
>
> - The fix for a stall bug introduced by a recent optimization in sched core
> (SM_IDLE).
>
> - Addition of /sys/kernel/sched_ext/enable_seq. While not a fix, it is a
> simple addition that distro people want to be able to tell whether an SCX
> scheduler has ever been loaded on the system.
>
> ----------------------------------------------------------------
> Andrea Righi (1):
> sched_ext: Provide a sysfs enable_seq counter
>
> Pat Somaru (1):
> sched, sched_ext: Disable SM_IDLE/rq empty path when scx_enabled()
>
> Tejun Heo (1):
> sched_ext: Fix build when !CONFIG_STACKTRACE
>
> Yu Liao (2):
> sched: Add dummy version of sched_group_set_idle()
> sched: Put task_group::idle under CONFIG_GROUP_SCHED_WEIGHT
>
> Documentation/scheduler/sched-ext.rst | 10 ++++++++++
> kernel/sched/core.c | 3 ++-
> kernel/sched/ext.c | 24 +++++++++++++++++++++---
> kernel/sched/sched.h | 10 ++++++----
> tools/sched_ext/scx_show_state.py | 1 +
> 5 files changed, 40 insertions(+), 8 deletions(-)
>
> --
> tejun
--
tejun
next prev parent reply other threads:[~2024-09-23 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 17:04 Tejun Heo
2024-09-23 17:18 ` Tejun Heo [this message]
2024-09-24 18:45 ` 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=ZvGi-Ciqmy8U5g_j@slm.duckdns.org \
--to=tj@kernel.org \
--cc=kernel-team@meta.com \
--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®