From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, Brenden Blanco <bblanco@plumgrid.com>,
Thomas Graf <tgraf@suug.ch>, Wangnan <wangnan0@huawei.com>,
He Kuang <hekuang@huawei.com>,
kernel-team@fb.com
Subject: Re: bpf debug info
Date: Tue, 6 Dec 2016 12:12:01 -0300 [thread overview]
Message-ID: <20161206151201.GD2399@kernel.org> (raw)
In-Reply-To: <20161129170115.GB22217@ast-mbp.thefacebook.com>
Em Tue, Nov 29, 2016 at 09:01:17AM -0800, Alexei Starovoitov escreveu:
> On Tue, Nov 29, 2016 at 04:11:32PM +0100, Daniel Borkmann wrote:
> > On 11/29/2016 07:42 AM, Alexei Starovoitov wrote:
> > >Notice that 'clang -S -o a.s' output and llvm-objdump disassembler
> > >were changed to use kernel verifier style, so now it should be easier
> > >to see what's going on.
> > Sounds really useful, is that scheduled for llvm 3.10 release?
> llvm 4.0 :)
> > That debugging info is stored in dwarf format into the obj, right?
> right.
> > Would be nice if also pahole could work on bpf object files.
>
> yeah. pahole need to be taught to recognize bpf e_machine type and relocations.
Coincidentally I'm testing some perf patches wrt builtin BPF and for
that I'm updating to llvm to 4.0, will take a look at what is involved
in that...
- Arnaldo
next prev parent reply other threads:[~2016-12-06 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 6:42 bpf debug info Alexei Starovoitov
2016-11-29 15:11 ` Daniel Borkmann
2016-11-29 15:38 ` Jakub Kicinski
2016-11-29 18:51 ` Alexei Starovoitov
2016-11-29 20:23 ` Daniel Borkmann
2016-11-30 0:28 ` Alexei Starovoitov
2016-11-29 17:01 ` Alexei Starovoitov
2016-12-06 15:12 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-13 19:38 Alexei Starovoitov
2016-12-13 19:55 ` Daniel Borkmann
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=20161206151201.GD2399@kernel.org \
--to=acme@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bblanco@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=hekuang@huawei.com \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=wangnan0@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.