The first ones are container based builds of tools/perf with and without libelfsupport. Where clang is available, it is also used to build perf with/withoutlibelf, and building with LIBCLANGLLVM=1 (built-in clang) with gcc and clangwhen clang and its devel libraries are installed.

The objtool and samples/bpf/ builds are disabled now that I'm switching fromusing the sources in a local volume to fetching them from a http server tobuild it inside the container, to make it easier to build in a container cluster.Those will come back later.

Several are cross builds, the ones with -x-ARCH and the android one, and thosemay not have all the features built, due to lack of multi-arch devel packages,available and being used so far on just a few, likedebian:experimental-x-{arm64,mipsel}.

The 'perf test' one will perform a variety of tests exercisingtools/perf/util/, tools/lib/{bpf,traceevent,etc}, as well as run perf commandswith a variety of command line event specifications to then intercept thesys_perf_event syscall to check that the perf_event_attr fields are set up asexpected, among a variety of other unit tests.

Then there is the 'make -C tools/perf build-test' ones, that build tools/perf/with a variety of feature sets, exercising the build with an incomplete set offeatures as well as with a complete one. It is planned to have it run on eachof the containers mentioned above, using some container orchestrationinfrastructure. Get in contact if interested in helping having this in place.