From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
dwarves@vger.kernel.org, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH dwarves 4/4] btf: add support for split BTF loading and encoding
Date: Fri, 13 Nov 2020 08:35:28 -0300 [thread overview]
Message-ID: <20201113113528.GA394182@kernel.org> (raw)
In-Reply-To: <CAEf4BzajM3Pg13uTF7cKOWfASvhOPOx85ufcchuDcGLEq8d9fQ@mail.gmail.com>
Em Wed, Nov 11, 2020 at 10:29:32AM -0800, Andrii Nakryiko escreveu:
> On Wed, Nov 11, 2020 at 4:19 AM Arnaldo Carvalho de Melo
> <acme@kernel.org> 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/
Done, thanks for the pinter.
- Arnaldo
next prev parent reply other threads:[~2020-11-13 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 5:25 [PATCH dwarves 0/4] Add split BTF support to pahole Andrii Nakryiko
2020-11-06 5:25 ` [PATCH dwarves 1/4] btf_encoder: fix array index type numbering Andrii Nakryiko
2020-11-06 5:25 ` [PATCH dwarves 2/4] libbtf: improve variable naming and error reporting when writing out BTF Andrii Nakryiko
2020-11-06 5:25 ` [PATCH dwarves 3/4] libbpf: update libbpf submodlue reference to latest master Andrii Nakryiko
2020-11-06 5:25 ` [PATCH dwarves 4/4] btf: add support for split BTF loading and encoding Andrii Nakryiko
2020-11-11 11:56 ` Arnaldo Carvalho de Melo
2020-11-11 12:19 ` Arnaldo Carvalho de Melo
2020-11-11 18:29 ` Andrii Nakryiko
2020-11-11 18:32 ` Arnaldo
2020-11-13 11:35 ` Arnaldo Carvalho de Melo [this message]
2020-11-11 18:27 ` Andrii Nakryiko
2020-11-11 18:34 ` Arnaldo
2020-11-11 18:50 ` Andrii Nakryiko
2020-11-10 23:34 ` [PATCH dwarves 0/4] Add split BTF support to pahole Andrii Nakryiko
2020-11-11 0:29 ` Arnaldo
2020-11-11 0:35 ` Andrii Nakryiko
2020-11-11 0:38 ` Arnaldo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201113113528.GA394182@kernel.org \
--to=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=kernel-team@fb.com \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox