[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m94EAn-xiPWJ1dRFTqcm6urBNNOPza94BmyYvp_5ti06uAZF0Izg2mBC9rpbc3PEfWWvDf7UyDt1x_2gB-7y3esTH3f54s05QBxcTXh4YhQ=@pm.me>
Date: Wed, 22 Jan 2025 19:10:00 +0000
From: Ihor Solodrai <ihor.solodrai@...me>
To: Tejun Heo <tj@...nel.org>
Cc: sched-ext@...a.com, kernel-team@...a.com, linux-kernel@...r.kernel.org, bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH sched_ext/for-6.13-fixes] sched_ext: Fix dsq_local_on selftest
On Tuesday, January 21st, 2025 at 5:40 PM, Tejun Heo <tj@...nel.org> wrote:
>
>
> Hello, sorry about the delay.
>
> On Wed, Jan 15, 2025 at 11:50:37PM +0000, Ihor Solodrai wrote:
> ...
>
> > 2025-01-15T23:28:55.8238375Z [ 5.334631] sched_ext: BPF scheduler "dsp_local_on" disabled (runtime error)
> > 2025-01-15T23:28:55.8243034Z [ 5.335420] sched_ext: dsp_local_on: SCX_DSQ_LOCAL[_ON] verdict target cpu 1 not allowed for kworker/u8:1[33]
>
>
> That's a head scratcher. It's a single node 2 cpu instance and all unbound
> kworkers should be allowed on all CPUs. I'll update the test to test the
> actual cpumask but can you see whether this failure is consistent or flaky?
I re-ran all the jobs, and all sched_ext jobs have failed (3/3).
Previous time only 1 of 3 runs failed.
https://github.com/kernel-patches/vmtest/actions/runs/12798804552/job/36016405680
>
> Thanks.
>
> --
> tejun
Powered by blists - more mailing lists