Research upstream kernel building with tuxmake
Antonio mentioned using custom containers is possible via --image
argument or TUXMAKE_IMAGE
env var. Our tarball building (especially handling selftests and dropping files that don't work with cross compilation) could use some simplification and it would be better to use some common tooling in case it exists.
tuxmake project: https://gitlab.com/Linaro/tuxmake
docs: https://tuxmake.org/
Figure out if we can use our Fedora/rawhide containers for building upstream tarballs, or what would need to change on either side for this to work. Since tuxmake is meant to work with primarily with base Debian containers, there may be some assumptions based on paths or available packages that don't work on Fedora. Antonio opened an issue for documenting the requirements that once resolved, should provide enough information to start here: Linaro/tuxmake#135 (closed)
We don't want to lose any functionality we have right now, mainly being able to use Fedora configs with optionally added kselftests config target (this should be possible but I didn't dig very deep) and being able to build selftest subsets and getting per-selftest results. A plus would be if our cross compile workarounds were handled as well but that's not a requirement.
Based on the results of this research, things can go multiple ways. Ideal outcome would be if we used tuxmake in our setup and our containers were officially supported for use with tuxmake (and this branch documented officially in tuxmake docs) so others using tuxmake could test the kernel with the state of art Fedora environment.