[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZwazfdmNiPmCnWUK@slm.duckdns.org>
Date: Wed, 9 Oct 2024 06:46:53 -1000
From: Tejun Heo <tj@...nel.org>
To: Björn Töpel <bjorn@...nel.org>
Cc: David Vernet <void@...ifault.com>, Shuah Khan <shuah@...nel.org>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Mark Brown <broonie@...nel.org>,
Björn Töpel <bjorn@...osinc.com>,
bpf@...r.kernel.org, linux-riscv@...ts.infradead.org,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: [PATCH v3] selftests: sched_ext: Add sched_ext as proper
selftest target
On Tue, Oct 08, 2024 at 05:35:18PM +0200, Björn Töpel wrote:
> From: Björn Töpel <bjorn@...osinc.com>
>
> The sched_ext selftests is missing proper cross-compilation support, a
> proper target entry, and out-of-tree build support.
>
> When building the kselftest suite, e.g.:
>
> make ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- \
> TARGETS=sched_ext SKIP_TARGETS="" O=/output/foo \
> -C tools/testing/selftests install
>
> or:
>
> make ARCH=arm64 LLVM=1 TARGETS=sched_ext SKIP_TARGETS="" \
> O=/output/foo -C tools/testing/selftests install
>
> The expectation is that the sched_ext is included, cross-built, the
> correct toolchain is picked up, and placed into /output/foo.
>
> In contrast to the BPF selftests, the sched_ext suite does not use
> bpftool at test run-time, so it is sufficient to build bpftool for the
> build host only.
>
> Add ARCH, CROSS_COMPILE, OUTPUT, and TARGETS support to the sched_ext
> selftest. Also, remove some variables that were unused by the
> Makefile.
>
> Signed-off-by: Björn Töpel <bjorn@...osinc.com>
Applied to sched_ext/for-6.12-fixes.
Thanks.
--
tejun
Powered by blists - more mailing lists