On Tue, Sep 29, 2020 at 5:03 PM Alexei Starovoitov <alexei.starovoitov@xxxxxxxxx> wrote: > > On Tue, Sep 29, 2020 at 04:28:39PM -0700, Andrii Nakryiko wrote: > > Add btf_dump__dump_type_raw() API that emits human-readable low-level BTF type > > information, same as bpftool output. bpftool is not switched to this API > > because bpftool still needs to perform all the same BTF type processing logic > > to do JSON output, so benefits are pretty much zero. > > If the only existing user cannot actually use such api it speaks heavily > against adding such api to libbpf. Comparing strings in tests is nice, but > could be done with C output just as well. It certainly can, it just won't save much code, because bpftool would still need to have a big switch over BTF type kinds to do JSON output. I can do such conversion, if you prefer. I'm also thinking about switching pahole to use this during BTF dedup verbose mode, if Arnaldo will be fine with changing output format a bit.
