From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH RFC v4 net-next 17/26] tracing: allow eBPF programs to be attached to events Date: Fri, 15 Aug 2014 11:50:49 -0700 Message-ID: References: <1407916658-8731-1-git-send-email-ast@plumgrid.com> <1407916658-8731-18-git-send-email-ast@plumgrid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Daniel Borkmann , "H. Peter Anvin" , Andrew Morton , Linux API , Chema Gonzalez , Eric Dumazet , "David S. Miller" , Brendan Gregg , Linus Torvalds , Steven Rostedt , LKML , Peter Zijlstra , Kees Cook , Network Development , Ingo Molnar To: Alexei Starovoitov Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Aug 15, 2014 10:36 AM, "Alexei Starovoitov" wrote: > > On Fri, Aug 15, 2014 at 10:20 AM, Andy Lutomirski wrote: > > The downside of this approach is that compat support might be > > difficult or impossible. > > Would do you mean by compat? 32-bit programs on 64-bit kernels? > There is no such concept for eBPF. All eBPF programs are always > operating on 64-bit registers. Doesn't the eBPF program need to know sizeof(long) to read these fields correctly? Or am I misunderstanding what the code does? --Andy