On Wed, Nov 11, 2020 at 4:19 AM Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote: > > Em Wed, Nov 11, 2020 at 08:56:27AM -0300, Arnaldo Carvalho de Melo escreveu: > > > > The entry for btf_encode/-J is missing, I'll add in a followup patch. > > > > Also I had to fixup ARGP_btf_base to 321 as I added this, to simplify > > the kernel scripts and Makefiles: > > > > $ pahole --numeric_version > > 118 > > $ > > Added this: > > [acme@five pahole]$ git diff > diff --git a/man-pages/pahole.1 b/man-pages/pahole.1 > index 20ee91fc911d4b39..f44c649924383a32 100644 > --- a/man-pages/pahole.1 > +++ b/man-pages/pahole.1 > @@ -181,6 +181,14 @@ the debugging information. > .B \-\-skip_encoding_btf_vars > Do not encode VARs in BTF. > > +.TP > +.B \-J, \-\-btf_encode > +Encode BTF information from DWARF, used in the Linux kernel build process when > +CONFIG_DEBUG_INFO_BTF=y is present, introduced in Linux v5.2. Used to implement > +features such as BPF CO-RE (Compile Once - Run Everywhere). > + > +See \fIhttp://vger.kernel.org/bpfconf2019_talks/bpf-core.pdf\fR. Can you please point to [0] instead? That linked presentation is already a bit out of date and will bitrot much faster. Blog post has at least a chance at being updated with relevant important stuff. Plus it has links both to the bpfconf2019 presentation, as well as some other resources (including your presentation). [0] https://nakryiko.com/posts/bpf-portability-and-co-re/ > + > .TP > .B \-\-btf_encode_force > Ignore those symbols found invalid when encoding BTF. > [acme@five pahole]$
