BTFhub, in collaboration with the BTFhub Archive repository, supplies BTF files for all published kernels that lack native support for embedded BTF. This joint effort ensures that even kernels without built-in BTF support can effectively leverage the benefits of eBPF programs, promoting compatibility across various kernel versions.
I think it could be valuable to have CI checks for btfhub-archive PRs. This would allow us to enforce some quality standards, such as:
no folder structure in the tarball
file naming within the the tarball
maybe checking the BTF itself, to ensure it was generated with the correct pahole arguments
I'm not sure there is a way to do this without having files in-tree of the btfhub-archive repo. This means consumers would need to ignore a .github folder (or equivalent).
I think it could be valuable to have CI checks for btfhub-archive PRs. This would allow us to enforce some quality standards, such as:
paholeargumentsI'm not sure there is a way to do this without having files in-tree of the btfhub-archive repo. This means consumers would need to ignore a
.githubfolder (or equivalent).