On Wed, 2018-10-31 at 11:53 -0700, Alexei Starovoitov wrote:
please define 'unsafe'
Correct. No BTF, I mostly had bpf calls going but didn't finish it
reasonably simple? ;)
I suspect it doesn't support bpf-to-bpf calls and BTF, right?
These were major additions that folks with custom loader
will be missing.
A lot more stuff to come with BTF, relocations, etc.
I don't think it will be feasible to replicate the same
in other libraries.
Hence everyone is highly encouraged to use libbpf.
c++, go or any other wrappers can go on top.
Whether they're kept as part of libbpf repo or repo next to it is
because we don't need it right now.
I understand the situation but this makes me a bit sad. I wrote the
loader originally to avoid 'unsafe' code in our project.
Not Go in the Go runtime :)