mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: sched-ext@lists.linux.dev
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>,
	linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: [PATCHSET sched_ext/for-7.4] sched_ext: Sync tools headers from the scx repo
Date: Tue, 29 Sep 2026 14:04:20 -1000	[thread overview]
Message-ID: <20260930000422.3350352-1-tj@kernel.org> (raw)

Hello,

The shared BPF headers in tools/sched_ext/include and the scx repo's
scheds/include have drifted apart since the last sync: the kernel gained a
size argument on scx_bpf_cid_topo(), scx_bpf_cid_node(), the lazy preemption
and proxy-exec flags and SCX_OPS_OPEN_OPTS(), while scx grew the cmask
helpers the cid-form schedulers use and the compat wrappers for the kfuncs
whose prototypes changed. This patchset copies the merged result back in.
The scx side is https://github.com/sched-ext/scx/pull/3856.

Patch 1 syncs the four shared headers and adds the two files they now depend
on, const-defs.h and features.bpf.h, and converts scx_qmap's cmask calls to
the three-operand form. Patch 2 syncs the four autogen enum headers, whose
task state lookups had been under a removed enum type.

Verified by building the kernel, tools/sched_ext and the sched_ext selftests
against the patched headers, and by a per-file diff showing every shared
file identical to the scx tree.

Based on sched_ext/for-7.4 (c6fe97c34a1a).

This patchset contains the following 2 patches.

 0001 sched_ext: Sync common and compat headers from the scx repo
 0002 sched_ext: Sync tools autogen enum headers from the scx repo

The patchset is also available in the following git branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-tools-header-sync

diffstat follows. Thanks.

 tools/sched_ext/include/scx/cid.bpf.h           | 689 ++++++++++++++++++++----
 tools/sched_ext/include/scx/common.bpf.h        |  90 +++-
 tools/sched_ext/include/scx/compat.bpf.h        |  63 +++
 tools/sched_ext/include/scx/compat.h            |  15 +-
 tools/sched_ext/include/scx/const-defs.h        |  20 +
 tools/sched_ext/include/scx/enum_defs.autogen.h |   3 +
 tools/sched_ext/include/scx/enums.autogen.bpf.h |  15 +-
 tools/sched_ext/include/scx/enums.autogen.h     |  20 +-
 tools/sched_ext/include/scx/enums_abi.autogen.h |   6 +
 tools/sched_ext/include/scx/features.bpf.h      |  29 +
 tools/sched_ext/scx_qmap.bpf.c                  |  14 +-
 11 files changed, 837 insertions(+), 127 deletions(-)

--
tejun

             reply	other threads:[~2026-09-30  0:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  0:04 Tejun Heo [this message]
2026-09-30  0:04 ` [PATCH 1/2] sched_ext: Sync common and compat " Tejun Heo
2026-09-30  0:04 ` [PATCH 2/2] sched_ext: Sync tools autogen enum " Tejun Heo
2026-09-30 23:47 ` [PATCHSET sched_ext/for-7.4] sched_ext: Sync tools " Tejun Heo

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=20260930000422.3350352-1-tj@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=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®