From: "Eelco Chaudron" <echaudro@redhat.com> To: "Alexei Starovoitov" <alexei.starovoitov@gmail.com> Cc: "Y Song" <ys114321@gmail.com>, "Yonghong Song" <yhs@fb.com>, Xdp <xdp-newbies@vger.kernel.org>, bpf <bpf@vger.kernel.org> Subject: Re: Trying the bpf trace a bpf xdp program Date: Thu, 19 Dec 2019 12:06:50 +0100 Message-ID: <B2161C36-B1A9-41B8-9D93-A18869649E25@redhat.com> (raw) In-Reply-To: <CAADnVQ+DHuDS2xZbjsEfBYX5t761dbCih6p-=NaCNU9OJEMk8A@mail.gmail.com> On 7 Dec 2019, at 17:51, Alexei Starovoitov wrote: > On Fri, Dec 6, 2019 at 5:05 AM Eelco Chaudron <echaudro@redhat.com> wrote: >> >> Thanks the hint that it should be the jitted arguments solved it… And >> you quick example worked, just in case some one else is playing with it, >> here is my working example: >> <SNIP> > This is great. Could you submit it as selftests/bpf ? Good idea, sent a patch out... > It will help others trying to do the same. > May be instead of bpf_debug() use global variables so the test will be > self checking ? > > Long term we should teach verifier to understand 'struct xdp_md*' > in addition to 'struct xdp_buff *'. That will help ease of use.
next prev parent reply index Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <E53E0693-1C3A-4B47-B205-DC8E5DAF3619@redhat.com> 2019-11-28 18:18 ` Alexei Starovoitov 2019-11-28 19:16 ` Eelco Chaudron 2019-11-28 19:47 ` Alexei Starovoitov 2019-11-29 16:30 ` Eelco Chaudron 2019-11-29 16:52 ` Yonghong Song 2019-12-02 16:34 ` Eelco Chaudron 2019-12-02 16:48 ` Yonghong Song 2019-12-04 13:19 ` Eelco Chaudron 2019-12-04 14:58 ` Yonghong Song 2019-12-04 18:01 ` Yonghong Song 2019-12-04 18:52 ` Eelco Chaudron 2019-12-05 12:40 ` Eelco Chaudron 2019-12-05 17:35 ` Y Song 2019-12-06 13:04 ` Eelco Chaudron 2019-12-07 16:51 ` Alexei Starovoitov 2019-12-19 11:06 ` Eelco Chaudron [this message] 2019-12-04 16:31 ` Andrii Nakryiko 2019-12-04 18:03 ` John Fastabend 2019-12-04 21:19 ` Andrii Nakryiko
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=B2161C36-B1A9-41B8-9D93-A18869649E25@redhat.com \ --to=echaudro@redhat.com \ --cc=alexei.starovoitov@gmail.com \ --cc=bpf@vger.kernel.org \ --cc=xdp-newbies@vger.kernel.org \ --cc=yhs@fb.com \ --cc=ys114321@gmail.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
BPF Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/bpf/0 bpf/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 bpf bpf/ https://lore.kernel.org/bpf \ bpf@vger.kernel.org public-inbox-index bpf Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.bpf AGPL code for this site: git clone https://public-inbox.org/public-inbox.git