Andrii Nakryiko
Andrii Nakryiko
We are using bootstrap version of bpftool (as it's smaller and builds faster), but it will be built for host system. So for cross-compilation we'd need to use final bpftool...
there is an upstream fix for this, I'll do upstream -> Github sync shortly and that should handle this problem
@jkoptimize if this still doesn't work, you can also try "typeless" ksym reference: ``` extern const void kernel_cpustat __ksym; ``` That shouldn't need BTF information, but will let you get...
We just recently released v1.6, I don't really have any immediate plans for v1.7 release, tbh. Which commit are you referring to?
@AlainKnaff thanks for the report. It's unfortunate, because include/linux/types.h that libbpf caries is meant to be a Linux-internal header, so it shouldn't be used by any other header. But unfortunately...
@alan-maguire can you please take a look?
btw, seems like your PR description is out of date, you do have kprobe fallback, no?
No, libbpf doesn't provide such a way, and it's better left to user to do this, because there is no single best way to do this. It will be up...
so thinking about this a bit more, I think we are mostly there already. Check out `ring__xxx()` APIs, which let you work with individual ringbufs that are part of ring_buffer...
a) ok, that's great! b) ok, understood :) #1338 is a prerequisite for this anyways, so let's put this on hold for now, thanks!