> On Fri, 31 Oct 2025 at 21:57, Jose E. Marchesi <[email protected]> > wrote: >> >> >> > On Tue, 28 Oct 2025 at 23:18, Jose E. Marchesi <[email protected]> >> > wrote: >> >> >> >> >> >> A question, bpftool is listed as a DEPENDENCY to >> >> >> >> 1) Generate vmlinux.h and >> >> 2) Generate skeletons when you do make check-bpf ... >> >> >> >> The bpftool in my Devuan system is too old, so it doesn't understand the >> >> skeleton gen command. >> >> >> >> Since bpftool is part of the kernel, would it be possible for >> >> bpf-vmtest-tool to also build it, make it available, generate vmlinux.h, >> >> etc? >> >> >> > >> > I can definitely add that. Would you prefer bpftool to be installed in >> > the shell’s $PATH, or just for internal use by the tool? >> > But, how should we handle which bpftool version to use? Should I store >> > a separate bpftool build for each kernel version, or have a single >> > shared one? >> > >> > I haven’t run into issues using Fedora’s bpftool with 6.x kernels, but >> > behavior across major releases might vary, so it might indeed be best >> > to use the bpftool build from that kernel version’s source. thoughts >> > ? >> >> AFAIK each kernel provides its own bpftool in linux/tools/bpf/bpftool, >> so I would build it and make it available for internal use. > > sure, i would also generate the vmlinux.h from the kernel image so > that we don't depend on any host vmlinux.h
That would be perfect yes. Thank you!
