Replies: 2 comments
-
The reason is that nobody had a use for it so far. Feel free to submit a PR if you want to add it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This won't help on programs loaded by ebpf-go itself, as we only marshal and load the types needed to construct func_infos. To replicate bpftool behaviour, you need the type info for arbitrary maps loaded by pin/id, correct? It would be nice to expose this through Map.Key() and .Value(), much like we do for MapSpec. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The mapInfo struct does not contain BTF information for the map its representing. However this information is accessible in the underlying sys/MapInfo struct.
The BTF information (BtfId, BtfVmlinuxValueTypeId) should be exposed to power use cases such as map dumping similar to how bpftool does it without having to locate the associated program that loaded it.
Is there a reason this information is not exposed?
Beta Was this translation helpful? Give feedback.
All reactions