[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed580e58-2853-561c-c3a3-29814c72ab03@iogearbox.net>
Date: Thu, 11 Apr 2019 09:51:47 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>,
Prashant Bhole <bhole_prashant_q7@....ntt.co.jp>
Cc: Alexei Starovoitov <ast@...nel.org>,
Quentin Monnet <quentin.monnet@...ronome.com>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next] tools/bpftool: show btf id in program
information
On 04/10/2019 05:39 PM, Jakub Kicinski wrote:
> On Wed, 10 Apr 2019 13:56:42 +0900, Prashant Bhole wrote:
>> Let's add a way to know whether a program has btf context.
>> Patch adds 'btf_id' in the output of program listing.
>> When btf_id is present, it means program has btf context.
>>
>> Sample output:
>> user@...t# bpftool prog list
>> 25: xdp name xdp_prog1 tag 539ec6ce11b52f98 gpl
>> loaded_at 2019-04-10T11:44:20+0900 uid 0
>> xlated 488B not jited memlock 4096B map_ids 23
>> btf_id 1
>>
>> Signed-off-by: Prashant Bhole <bhole_prashant_q7@....ntt.co.jp>
>
> Acked-by: Jakub Kicinski <jakub.kicinski@...ronome.com>
Applied, thanks!
What would be the plan for the maps listing?
I think what we could also potentially have is some way to dump
the BTF type info based on such above id. Perhaps it would make
sense to similarly share the verifier's printer with bpftool?
Powered by blists - more mailing lists