All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Vernet <void@manifault.com>,
	Andrea Righi <arighi@nvidia.com>,
	Changwoo Min <changwoo@igalia.com>,
	Emil Tsalapatis <emil@etsalapatis.com>,
	David Dai <david.dai@linux.dev>,
	sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sched_ext: Another fix for v7.3-rc4
Date: Sat, 26 Sep 2026 22:49:04 -1000	[thread overview]
Message-ID: <b633964a6f8f06d64bee4227394d6218@kernel.org> (raw)

Hello,

The following changes since commit 4409a85735cdca5c4c400c0dad1feee091872eee:

  sched_ext: Count SCX_EV_SUB_BYPASS_DISPATCH in the dispatch fallback (2026-09-23 08:16:10 -1000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git tags/sched_ext-for-7.3-rc4-fixes-2

for you to fetch changes up to 94480606a677deb68d5622cf0ded88626514b3f2:

  sched_ext: Add a size argument to scx_bpf_cid_topo() so struct scx_cid_topo can grow (2026-09-26 10:09:12 -1000)

----------------------------------------------------------------
sched_ext: Fixes for v7.3-rc4

- The CPU topology helper for BPF schedulers took no buffer size, so its
  structure couldn't grow without breaking schedulers built against the
  older layout. Add a size argument.

----------------------------------------------------------------
Tejun Heo (1):
      sched_ext: Add a size argument to scx_bpf_cid_topo() so struct scx_cid_topo can grow

 kernel/sched/ext/cid.c                   | 26 ++++++++++++++++----------
 kernel/sched/ext/types.h                 |  4 ++++
 tools/sched_ext/include/scx/common.bpf.h |  2 +-
 3 files changed, 21 insertions(+), 11 deletions(-)

-- 
tejun

             reply	other threads:[~2026-09-27  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27  8:49 Tejun Heo [this message]
2026-09-27 19:47 ` [GIT PULL] sched_ext: Another fix for v7.3-rc4 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=b633964a6f8f06d64bee4227394d6218@kernel.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=david.dai@linux.dev \
    --cc=emil@etsalapatis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.