> > Have you considered generating kernel BTF with fields that are accessed > > by bpf prog only and replacing all other fields with padding ? > > That is exactly the result of our final BTF file. We only include the > fields and types being used by the given eBPF object: A full explanation on this here: https://github.com/aquasecurity/btfhub/tree/main/tools#how-to-use-libbpf-co-re-relocations-to-build-a-btf-file
