mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.16-rc1
Date: Wed, 4 Jun 2025 08:54:56 -1000	[thread overview]
Message-ID: <aECWgEYwOhciTIuk@slm.duckdns.org> (raw)

The following changes since commit 0f70f5b08a47a3bc1a252e5f451a137cde7c98ce:

  Merge tag 'pull-automount' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2025-05-30 15:38:29 -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.16-rc1-fixes

for you to fetch changes up to 9960be72a54cf0e4d47abdd4cacd1278835a3bb4:

  sched_ext: idle: Skip cross-node search with !CONFIG_NUMA (2025-06-03 08:22:27 -1000)

----------------------------------------------------------------
sched_ext: Fixes for v6.16-rc1

Two fixes in the built-in idle selection helpers.

- Fix prev_cpu handling to guarantee that idle selection never returns a CPU
  that's not allowed.

- Skip cross-node search when !NUMA which could lead to infinite looping due
  to a bug in NUMA iterator.

----------------------------------------------------------------
Andrea Righi (2):
      sched_ext: idle: Properly handle invalid prev_cpu during idle selection
      sched_ext: idle: Skip cross-node search with !CONFIG_NUMA

 kernel/sched/ext_idle.c | 37 +++++++++++++++++++------------------
 1 file changed, 19 insertions(+), 18 deletions(-)

-- 
tejun

             reply	other threads:[~2025-06-04 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 18:54 Tejun Heo [this message]
2025-06-04 20:09 ` 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=aECWgEYwOhciTIuk@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

all inboxes | Powered by JetHome®