From: Christian Loehle <christian.loehle@arm.com>
To: Tejun Heo <tj@kernel.org>
Cc: arighi@nvidia.com, void@manifault.com,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev,
changwoo@igalia.com, hodgesd@meta.com, mingo@redhat.com,
peterz@infradead.org, jake@hillion.co.uk
Subject: Re: [PATCH v4 1/3] sched_ext: Introduce scx_bpf_cpu_rq_locked()
Date: Tue, 12 Aug 2025 10:07:46 +0100 [thread overview]
Message-ID: <356a3c25-9c7c-41a5-a88e-ceeaf8405641@arm.com> (raw)
In-Reply-To: <aJp-2TPbNKO3k_lq@slm.duckdns.org>
On 8/12/25 00:38, Tejun Heo wrote:
> Hello,
>
> On Mon, Aug 11, 2025 at 10:21:48PM +0100, Christian Loehle wrote:
>> +/**
>> + * scx_bpf_cpu_rq_locked - Fetch the locked rq of a CPU
>> + * @cpu: CPU of the rq
>> + */
>> +__bpf_kfunc struct rq *scx_bpf_cpu_rq_locked(s32 cpu)
>> +{
>> + struct rq *rq;
>> +
>> + if (!kf_cpu_valid(cpu, NULL))
>> + return NULL;
>> +
>> + preempt_disable();
>> + rq = cpu_rq(cpu);
>> + if (rq != scx_locked_rq()) {
>> + scx_kf_error("Accessing not locked rq %d", cpu);
>> + rq = NULL;
>> + }
>> + preempt_enable();
>> + return rq;
>> +}
>
> Do we need @cpu? What do you think about making the function not take any
> arguments and just return the locked rq?
Indeed now that this no longer has to be a drop-in replacement.
next prev parent reply other threads:[~2025-08-12 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 21:21 [PATCH v4 0/3] sched_ext: Harden scx_bpf_cpu_rq() Christian Loehle
2025-08-11 21:21 ` [PATCH v4 1/3] sched_ext: Introduce scx_bpf_cpu_rq_locked() Christian Loehle
2025-08-11 23:38 ` Tejun Heo
2025-08-12 9:07 ` Christian Loehle [this message]
2025-08-11 21:21 ` [PATCH v4 2/3] sched_ext: Provide scx_bpf_task_acquire_remote_curr() Christian Loehle
2025-08-11 21:21 ` [PATCH v4 3/3] sched_ext: deprecation warn for scx_bpf_cpu_rq() Christian Loehle
2025-08-12 8:00 ` [PATCH v4 0/3] sched_ext: Harden scx_bpf_cpu_rq() Peter Zijlstra
2025-08-12 11:40 ` Christian Loehle
2025-08-12 13:36 ` 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=356a3c25-9c7c-41a5-a88e-ceeaf8405641@arm.com \
--to=christian.loehle@arm.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=hodgesd@meta.com \
--cc=jake@hillion.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®