mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Feng Yang <yangfeng59949@163.com>
To: arighi@nvidia.com
Cc: changwoo@igalia.com, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, sched-ext@lists.linux.dev,
	shuah@kernel.org, tj@kernel.org, void@manifault.com,
	yangfeng59949@163.com
Subject: Re: [PATCH] selftests/sched_ext: Fix the incorrect logic validation
Date: Mon,  2 Mar 2026 16:41:30 +0800	[thread overview]
Message-ID: <20260302084130.480694-1-yangfeng59949@163.com> (raw)
In-Reply-To: <aaVAhdw3ZO5kHJ32@gpd4>

On Mon, 2 Mar 2026 08:47:17 +0100, Andrea Righi wrote:
> On Mon, Mar 02, 2026 at 02:48:51PM +0800, Feng Yang wrote:
> > From: Feng Yang <yangfeng@kylinos.cn>
> > 
> > When __COMPAT_scx_bpf_pick_idle_cpu_node selects an idle CPU,
> > it reports that the CPU should be marked as busy.
> > 
> > Fixes: 5ae5161820e5 ("selftests/sched_ext: Add NUMA-aware scheduler test")
> > Signed-off-by: Feng Yang <yangfeng@kylinos.cn>
> > ---
> >  tools/testing/selftests/sched_ext/numa.bpf.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/tools/testing/selftests/sched_ext/numa.bpf.c b/tools/testing/selftests/sched_ext/numa.bpf.c
> > index a79d86ed54a1..98423628b05c 100644
> > --- a/tools/testing/selftests/sched_ext/numa.bpf.c
> > +++ b/tools/testing/selftests/sched_ext/numa.bpf.c
> > @@ -44,12 +44,12 @@ s32 BPF_STRUCT_OPS(numa_select_cpu,
> >  	 */
> >  	cpu = __COMPAT_scx_bpf_pick_idle_cpu_node(p->cpus_ptr, node,
> >  					__COMPAT_SCX_PICK_IDLE_IN_NODE);
> > -	if (cpu < 0)
> > +	if (cpu < 0) {
> >  		cpu = __COMPAT_scx_bpf_pick_any_cpu_node(p->cpus_ptr, node,
> >  						__COMPAT_SCX_PICK_IDLE_IN_NODE);
> > -
> > -	if (is_cpu_idle(cpu, node))
> > -		scx_bpf_error("CPU %d should be marked as busy", cpu);
> > +		if (is_cpu_idle(cpu, node))
> > +			scx_bpf_error("CPU %d should be marked as busy", cpu);
> > +	}
> 
> No, this is not correct. The CPU returned by scx_bpf_pick_idle_cpu_node()
> should be marked as busy at this point (bit is set in the idle cpumask),
> essentially it has been reserved/allocated by the caller.

Okay, I misunderstood.
The CI test of this patch (https://patchwork.kernel.org/project/netdevbpf/list/?series=1058866&state=*) 
resulted in the error "CPU 0 should be marked as busy"(https://github.com/kernel-patches/bpf/actions/runs/22548310848/job/65314767856),
but I don't see the connection between them that would cause this error. Could you explain why this happens?

Thanks,
Feng

> Maybe we can add a comment if we think it's not clear enough, but the
> original code looks correct.
> 
> >  
> >  	if (__COMPAT_scx_bpf_cpu_node(cpu) != node)
> >  		scx_bpf_error("CPU %d should be in node %d", cpu, node);
> > -- 
> > 2.43.0
> > 
> 
> Thanks,
> -Andrea


  reply	other threads:[~2026-03-02  8:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  6:48 Feng Yang
2026-03-02  7:47 ` Andrea Righi
2026-03-02  8:41   ` Feng Yang [this message]
2026-03-02 15:18     ` Andrea Righi
2026-03-03  2:31       ` Feng Yang

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=20260302084130.480694-1-yangfeng59949@163.com \
    --to=yangfeng59949@163.com \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=shuah@kernel.org \
    --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®