Re: [RFC PATCH 4/6] tools: build kernel selftests in tools_build

[Shuah Khan <skhan@linuxfoundation.org>]

On 10/11/26 17:36, Sasha Levin wrote:
> Add a "Kernel selftests" sub-menu with one entry per selftests directory
> that builds with only a C library and does not write into the source
> tree. Each is built as "make kselftest-all" builds it, with KHDR_INCLUDES
> pointing at the UAPI headers installed in the object tree, but by its own
> make, so the selected ones build in parallel. Selftests whose Makefile
> does not use KHDR_INCLUDES still build against the C library's copy of
> the UAPI headers.
> 
> The selftests do not track header dependencies, so a selftest is built
> again from scratch when its own directory, a header or makefile any
> selftest may share, or a kernel source it includes directly (the vDSO
> test includes the architecture's vDSO code) is newer than its last
> build.

Is there a way you can fold in kselftest_deps.sh run into this
so users know why some tests didn't build. Also we want to make
sure kselftest build doesn't fail if a test fails to build to
keep the current kselftest build behavior.

tools/testing/selftests/kselftest_deps.sh

> 
> Selftests that need libraries beyond the C library, a vmlinux with BTF,
> or a sanitizer runtime are left out for now.

Great. That is good for this round.

thanks,
-- Shuah