Sched_ext development
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: sashiko-bot@kernel.org
Cc: Tejun Heo <tj@kernel.org>, sched-ext@lists.linux.dev
Subject: Re: [PATCH 2/2] sched_ext: Maintain an online cid mask in the scheduler arena
Date: Tue, 15 Sep 2026 06:54:12 -1000	[thread overview]
Message-ID: <a3c4830e2eb2525d37e3327b628ae73c@kernel.org> (raw)
In-Reply-To: <20260915085819.5DB991F000FF@smtp.kernel.org>

On Tue, Sep 15, 2026 at 08:58:18AM +0000, sashiko-bot@kernel.org wrote:
> Does casting mask->bits to an unsigned long pointer corrupt the bitmask
> layout on 32-bit big-endian architectures?

The mask is only allocated for schedulers with an arena and BPF arena
support is 64bit only, so unsigned long is always 64bit here.

Thanks.

--
tejun

  reply	other threads:[~2026-09-15 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  8:27 [PATCHSET v2 sched_ext/for-7.3-fixes] sched_ext: Idle claim recovery and online cid mask Tejun Heo
2026-09-15  8:27 ` [PATCH 1/2] sched_ext: scx_qmap: Restore unused idle claims from ops.dispatch() Tejun Heo
2026-09-15  8:27 ` [PATCH 2/2] sched_ext: Maintain an online cid mask in the scheduler arena Tejun Heo
2026-09-15  8:58   ` sashiko-bot
2026-09-15 16:54     ` Tejun Heo [this message]
2026-09-15 12:27 ` [PATCHSET v2 sched_ext/for-7.3-fixes] sched_ext: Idle claim recovery and online cid mask Andrea Righi
2026-09-15 17:01 ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2026-09-14 23:42 [PATCHSET sched_ext/for-7.3-fixes] sched_ext: Idle repick notifications " Tejun Heo
2026-09-14 23:42 ` [PATCH 2/2] sched_ext: Maintain an online cid mask in the scheduler arena Tejun Heo
2026-09-15  0:03   ` sashiko-bot
2026-09-15  5:44   ` Andrea Righi

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=a3c4830e2eb2525d37e3327b628ae73c@kernel.org \
    --to=tj@kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sched-ext@lists.linux.dev \
    /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