From: Tejun Heo <tj@kernel.org>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: "David Vernet" <void@manifault.com>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Mark Brown" <broonie@kernel.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: [PATCH v3] selftests: sched_ext: Add sched_ext as proper selftest target
Date: Wed, 9 Oct 2024 06:46:53 -1000 [thread overview]
Message-ID: <ZwazfdmNiPmCnWUK@slm.duckdns.org> (raw)
In-Reply-To: <20241008153519.1270862-1-bjorn@kernel.org>
On Tue, Oct 08, 2024 at 05:35:18PM +0200, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.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@rivosinc.com>
Applied to sched_ext/for-6.12-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2024-10-09 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 15:35 [PATCH v3] selftests: sched_ext: Add sched_ext as proper selftest target Björn Töpel
2024-10-08 20:09 ` Shuah Khan
2024-10-08 20:38 ` David Vernet
2024-10-09 16:21 ` Mark Brown
2024-10-09 16:46 ` Tejun Heo [this message]
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=ZwazfdmNiPmCnWUK@slm.duckdns.org \
--to=tj@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=shuah@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