mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Changwoo Min <changwoo@igalia.com>
To: Tejun Heo <tj@kernel.org>
Cc: void@manifault.com, arighi@nvidia.com, emil@etsalapatis.com,
	kernel-dev@igalia.com, sched-ext@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: allow ops.cgroup_set_bandwidth() to be sleepable
Date: Tue, 18 Aug 2026 23:15:59 +0900	[thread overview]
Message-ID: <2f65d156-07ad-40aa-9ae1-2e14f836cf69@igalia.com> (raw)
In-Reply-To: <9ffe41fba1d0462a27443e95c5e3e03b@kernel.org>

Hello,

On 8/18/26 2:53 AM, Tejun Heo wrote:
> Hello,
> 
> On Tue, Aug 18, 2026 at 02:09:41AM +0900, Changwoo Min wrote:
>> +/*
>> + * Capability marker for userspace. The sleepable allowance for
>> + * ops.cgroup_set_bandwidth() (see bpf_scx_check_member()) is a verifier
>> + * property with no other symbol a scheduler can probe, so this no-op function
>> + * exists solely so its presence in the kernel's BTF can be detected. It has no
>> + * callers; __used keeps it from being optimized away.
>> + */
>> +__used void scx_cgroup_set_bandwidth_may_sleep(void) {}
> 
> __used only prevents the compiler from dropping the function. With
> CONFIG_LD_DEAD_CODE_DATA_ELIMINATION, the linker can still garbage
> collect its section, so please add __retain too (cf. __bpf_kfunc).
> 
> Also, we'll likely accumulate more of these markers over time, so let's
> give them a shared prefix - scx_compat_marker_ or something like that -
> and collect them in one place, maybe towards the end of ext.c next to
> the module init code.

Thanks for the comments. I will address these two and send v2 shortly.
Regarding the sashiko review, I think that needs to be addressed
separately.

Regards,
Changwoo Min

      reply	other threads:[~2026-08-18 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 17:09 Changwoo Min
2026-08-17 17:53 ` Tejun Heo
2026-08-18 14:15   ` Changwoo Min [this message]

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=2f65d156-07ad-40aa-9ae1-2e14f836cf69@igalia.com \
    --to=changwoo@igalia.com \
    --cc=arighi@nvidia.com \
    --cc=emil@etsalapatis.com \
    --cc=kernel-dev@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=tj@kernel.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®