mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Christian Loehle <christian.loehle@arm.com>
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 v5 2/3] sched_ext: Introduce scx_bpf_remote_curr()
Date: Wed, 3 Sep 2025 05:55:33 -1000	[thread overview]
Message-ID: <aLhk9Ugqu4ExvQNK@slm.duckdns.org> (raw)
In-Reply-To: <20250901132605.2282650-4-christian.loehle@arm.com>

Hello,

On Mon, Sep 01, 2025 at 02:26:03PM +0100, Christian Loehle wrote:
> +/**
> + * scx_bpf_remote_curr - Return remote CPU's curr task
> + * @cpu: CPU of interest
> + *
> + * Callers must hold RCU read lock (KF_RCU).
> + */
> +__bpf_kfunc struct task_struct *scx_bpf_remote_curr(s32 cpu)

And name this scx_bpf_cpu_curr().

Thanks.

-- 
tejun

  parent reply	other threads:[~2025-09-03 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 13:26 [PATCH v4 0/3] sched_ext: Harden scx_bpf_cpu_rq() Christian Loehle
2025-09-01 13:26 ` [PATCH v5 " Christian Loehle
2025-09-01 13:38   ` Christian Loehle
2025-09-01 13:26 ` [PATCH v5 1/3] sched_ext: Introduce scx_bpf_cpu_rq_locked() Christian Loehle
2025-09-03 15:54   ` Tejun Heo
2025-09-01 13:26 ` [PATCH v5 2/3] sched_ext: Introduce scx_bpf_remote_curr() Christian Loehle
2025-09-02  5:43   ` Andrea Righi
2025-09-03 15:55   ` Tejun Heo [this message]
2025-09-01 13:26 ` [PATCH v5 3/3] sched_ext: deprecation warn for scx_bpf_cpu_rq() Christian Loehle
2025-09-03 15:56   ` Tejun Heo
2025-09-03 20:37     ` Christian Loehle
2025-09-01 13:26 ` [PATCH v5 0/3] sched_ext: Harden scx_bpf_cpu_rq() Christian Loehle

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=aLhk9Ugqu4ExvQNK@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=christian.loehle@arm.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=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®