From: Andrea Righi <arighi@nvidia.com>
To: Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Alexei Starovoitov <ast@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: selftests/sched_ext: testing on BPF CI
Date: Wed, 29 Jan 2025 08:27:02 +0100 [thread overview]
Message-ID: <Z5nYRj1L4h1KCWE1@gpd3> (raw)
In-Reply-To: <3fb44500b87b0f1d8360bc7a1f3ae972d3c5282f@linux.dev>
Hi Ihor,
On Wed, Jan 29, 2025 at 12:21:43AM +0000, Ihor Solodrai wrote:
> Hi Tejun, Andrea.
>
> I tested a couple of variants of bpf-next + sched_ext source tree,
> just sharing the results.
Thanks for testing!
>
> I found a working state: BPF CI pipeline ran successfully twice
> (that's 8 build + run of selftests/sched_ext/runner in total).
Ok.
>
> Working state requires most patches between sched_ext/master and
> sched_ext/for-6.14-fixes [1], and also the patch
> "tools/sched_ext: Receive updates from SCX repo" [2]
>
> On plain bpf-next the dsp_local_on test fails [3].
> Without the patch [2] there is a build error [4]: missing
> SCX_ENUM_INIT definition.
We definitely need all the patches in sched_ext/for-6.14-fixes. I think
once Tejun sends the PR and we land the for-6.14-fixes upstream we should
reach a stable state with the sched_ext selftests. I don't have any other
additional pending fix at the moment.
>
> We probably don't want to enable selftests/sched_ext on BPF CI with
> that many "temporary" patches. I suggest to wait until all of this is
> merged upstream.
Sounds reasonable to me. Tejun?
>
> You can check the full list of patches here:
> https://github.com/kernel-patches/vmtest/pull/332/files
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/log/?h=for-6.14-fixes
> [2] https://lore.kernel.org/all/Z1ucTqJP8IeIXZql@slm.duckdns.org/
> [3] https://github.com/kernel-patches/vmtest/actions/runs/13019837022
> [4] https://github.com/kernel-patches/vmtest/actions/runs/13020458479
Thanks,
-Andrea
next prev parent reply other threads:[~2025-01-29 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 0:21 selftests/sched_ext: testing on BPF CI Ihor Solodrai
2025-01-29 7:27 ` Andrea Righi [this message]
2025-01-29 16:19 ` Tejun Heo
2025-05-02 21:40 ` Ihor Solodrai
2025-05-03 5:41 ` 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=Z5nYRj1L4h1KCWE1@gpd3 \
--to=arighi@nvidia.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.