Em Wed, Oct 25, 2023 at 02:43:02PM -0300, Arnaldo Carvalho de Melo escreveu: > $ cp vmlinux.v5.19.0-rc5+ vmlinux.v5.19.0-rc5+.enum64 ; pahole --btf_encode --btf_features=enum64 vmlinux.v5.19.0-rc5+.enum64 > $ > I tried using --btf_encode_detached=file but then couldn't find a way to > make 'bpftool btf' to consume detached BTF, it seems that "file" means > "ELF file containing BTF" so I copied the original file to then reencode > BTF selecting just the enum64 feature, the resulting file continues to > have the original DWARF and the BTF using that --btf_features set: This was another symptom of me using a random old bpftool, using upstream I get what is expected: $ pahole --btf_encode_detached=vmlinux.v5.19.0-rc5+.enum64 --btf_features=enum64 vmlinux.v5.19.0-rc5+ $ bpftool btf dump file vmlinux.v5.19.0-rc5+.enum64 format raw | wc -l 290975 $ file vmlinux.v5.19.0-rc5+.enum64 vmlinux.v5.19.0-rc5+.enum64: data $ [acme@quaco pahole]$ bpftool btf dump file vmlinux.v5.19.0-rc5+.enum64 format raw | grep -w ENUM64 [4266] ENUM64 'perf_event_sample_format' encoding=UNSIGNED size=8 vlen=27 [5089] ENUM64 '(anon)' encoding=UNSIGNED size=8 vlen=11 [6727] ENUM64 '(anon)' encoding=SIGNED size=8 vlen=28 [27943] ENUM64 '(anon)' encoding=UNSIGNED size=8 vlen=3 [31242] ENUM64 'netdev_priv_flags' encoding=UNSIGNED size=8 vlen=33 [31438] ENUM64 'perf_callchain_context' encoding=UNSIGNED size=8 vlen=7 [38853] ENUM64 'hmm_pfn_flags' encoding=UNSIGNED size=8 vlen=7 [56830] ENUM64 'ib_uverbs_device_cap_flags' encoding=UNSIGNED size=8 vlen=25 [60295] ENUM64 'blake2b_iv' encoding=UNSIGNED size=8 vlen=8 [63498] ENUM64 '(anon)' encoding=UNSIGNED size=8 vlen=31 [93914] ENUM64 '(anon)' encoding=SIGNED size=8 vlen=172 [acme@quaco pahole]$ So sorry for the noise about this. - Arnaldo
