From: Jiri Olsa <jolsa@redhat.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Andrii Nakryiko <andriin@fb.com>, Yonghong Song <yhs@fb.com>,
Martin KaFai Lau <kafai@fb.com>
Subject: Re: [PATCH] bpftool: Allow to read btf as raw data
Date: Fri, 25 Oct 2019 22:03:51 +0200 [thread overview]
Message-ID: <20191025200351.GA31835@krava> (raw)
In-Reply-To: <20191025113901.5a7e121e@cakuba.hsd1.ca.comcast.net>
On Fri, Oct 25, 2019 at 11:39:01AM -0700, Jakub Kicinski wrote:
> On Thu, 24 Oct 2019 15:30:25 +0200, Jiri Olsa wrote:
> > The bpftool interface stays the same, but now it's possible
> > to run it over BTF raw data, like:
> >
> > $ bpftool btf dump file /sys/kernel/btf/vmlinux
> > [1] INT '(anon)' size=4 bits_offset=0 nr_bits=32 encoding=(none)
> > [2] INT 'long unsigned int' size=8 bits_offset=0 nr_bits=64 encoding=(none)
> > [3] CONST '(anon)' type_id=2
> >
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
>
> Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
[root@ibm-z-107 bpftool]# ./bpftool btf dump file /sys/kernel/btf/vmlinux | head -3
[1] INT '(anon)' size=4 bits_offset=0 nr_bits=32 encoding=(none)
[2] INT 'long unsigned int' size=8 bits_offset=0 nr_bits=64 encoding=(none)
[3] CONST '(anon)' type_id=2
[root@ibm-z-107 bpftool]# lscpu | grep Endian
Byte Order: Big Endian
thanks,
jirka
next prev parent reply other threads:[~2019-10-25 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 13:30 [PATCH] bpftool: Allow to read btf as raw data Jiri Olsa
2019-10-24 17:55 ` Jakub Kicinski
2019-10-25 7:15 ` Jiri Olsa
2019-10-25 5:10 ` Andrii Nakryiko
2019-10-25 18:39 ` Jakub Kicinski
2019-10-25 20:03 ` Jiri Olsa [this message]
2019-10-26 18:42 ` Jakub Kicinski
2019-10-25 21:40 ` 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=20191025200351.GA31835@krava \
--to=jolsa@redhat.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.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.