BTF as a type format limits few types like BTF_TYPE_FWD which is generated when a type is declared in one file but defined in another. Seen in Cilium codebase.
Can we improve the BTF enrichment to capture where the BTF_TYPE_FWD leads to and create its mapping.
Do we need source code level view into the module for FWD type?
If so will need to integrate with the OPENED source code extractor to infer the FWD type information. Else, check if the type system (pahole) could be extended to have better support for the FWD type with a patch, the name of FWD types need to be same so it can be used to link the types.
BTF as a type format limits few types like BTF_TYPE_FWD which is generated when a type is declared in one file but defined in another. Seen in Cilium codebase.
Can we improve the BTF enrichment to capture where the BTF_TYPE_FWD leads to and create its mapping.
Do we need source code level view into the module for FWD type?
If so will need to integrate with the OPENED source code extractor to infer the FWD type information. Else, check if the type system (pahole) could be extended to have better support for the FWD type with a patch, the name of FWD types need to be same so it can be used to link the types.