[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191025071526.GB31679@krava>
Date: Fri, 25 Oct 2019 09:15:26 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Jiri Olsa <jolsa@...nel.org>, Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org,
bpf@...r.kernel.org, Andrii Nakryiko <andriin@...com>,
Yonghong Song <yhs@...com>, Martin KaFai Lau <kafai@...com>
Subject: Re: [PATCH] bpftool: Allow to read btf as raw data
On Thu, Oct 24, 2019 at 10:55:37AM -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@...nel.org>
> > ---
> > v3 changes:
> > - fix title
> >
> > v2 changes:
> > - added is_btf_raw to find out which btf__parse_* function to call
> > - changed labels and error propagation in btf__parse_raw
> > - drop the err initialization, which is not needed under this change
>
>
> Aw, this is v3? Looks like I replied to the older now, such confusion :)
yea, that went well.. sry, missed the v3 in title
jirka
Powered by blists - more mailing lists