Re: bpf debug info

2016-12-13 Thread Daniel Borkmann
On 12/13/2016 08:38 PM, Alexei Starovoitov wrote: On Tue, Nov 29, 2016 at 9:01 AM, Alexei Starovoitov wrote: If I try to run samples/bpf/test_cls_bpf.sh the verifier will complain: R0=imm0,min_value=0,max_value=0 R1=pkt(id=0,off=0,r=42) R2=pkt_end 112: (0f) r4 += r3 113: (0f) r1 += r4 114: (b7)

Re: bpf debug info

2016-12-13 Thread Alexei Starovoitov
On Tue, Nov 29, 2016 at 9:01 AM, Alexei Starovoitov wrote: >> >If I try to run samples/bpf/test_cls_bpf.sh the verifier will complain: >> >R0=imm0,min_value=0,max_value=0 R1=pkt(id=0,off=0,r=42) R2=pkt_end >> >112: (0f) r4 += r3 >> >113: (0f) r1 += r4 >> >114: (b7) r0 = 2 >> >115: (69) r2 = *(u16

Re: bpf debug info

2016-12-06 Thread Arnaldo Carvalho de Melo
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 ver

Re: bpf debug info

2016-11-29 Thread Alexei Starovoitov
On Tue, Nov 29, 2016 at 09:23:10PM +0100, Daniel Borkmann wrote: > On 11/29/2016 07:51 PM, Alexei Starovoitov wrote: > >On Tue, Nov 29, 2016 at 03:38:18PM +, Jakub Kicinski wrote: > [...] > So next step is to improve verifier messages to be more human friendly. > The step after is to in

Re: bpf debug info

2016-11-29 Thread Daniel Borkmann
On 11/29/2016 07:51 PM, Alexei Starovoitov wrote: On Tue, Nov 29, 2016 at 03:38:18PM +, Jakub Kicinski wrote: [...] So next step is to improve verifier messages to be more human friendly. The step after is to introduce BPF_COMMENT pseudo instruction that will be ignored by the interpreter y

Re: bpf debug info

2016-11-29 Thread Alexei Starovoitov
On Tue, Nov 29, 2016 at 03:38:18PM +, Jakub Kicinski wrote: > > >>> [...] > > > So next step is to improve verifier messages to be more human friendly. > > > The step after is to introduce BPF_COMMENT pseudo instruction > > > that will be ignored by the interpreter yet it will contain the text

Re: bpf debug info

2016-11-29 Thread Alexei Starovoitov
On Tue, Nov 29, 2016 at 04:11:32PM +0100, Daniel Borkmann wrote: > On 11/29/2016 07:42 AM, Alexei Starovoitov wrote: > [...] > >The support for debug information in BPF was recently added to llvm. > > > >In order to use it recompile bpf programs with the following patch > >in samples/bpf/Makefile >

Re: bpf debug info

2016-11-29 Thread Jakub Kicinski
On Tue, 29 Nov 2016 16:11:32 +0100, Daniel Borkmann wrote: > On 11/29/2016 07:42 AM, Alexei Starovoitov wrote: > [...] > > The support for debug information in BPF was recently added to llvm. > > > > In order to use it recompile bpf programs with the following patch > > in samples/bpf/Makefile > >

Re: bpf debug info

2016-11-29 Thread Daniel Borkmann
On 11/29/2016 07:42 AM, Alexei Starovoitov wrote: [...] The support for debug information in BPF was recently added to llvm. In order to use it recompile bpf programs with the following patch in samples/bpf/Makefile @@ -155,4 +155,4 @@ $(obj)/%.o: $(src)/%.c $(CLANG) $(NOSTDINC_FLAGS) $

bpf debug info

2016-11-28 Thread Alexei Starovoitov
Hi All, The support for debug information in BPF was recently added to llvm. In order to use it recompile bpf programs with the following patch in samples/bpf/Makefile @@ -155,4 +155,4 @@ $(obj)/%.o: $(src)/%.c $(CLANG) $(NOSTDINC_FLAGS) $(LINUXINCLUDE) $(EXTRA_CFLAGS) \ -