From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757062AbaIQWQM (ORCPT ); Wed, 17 Sep 2014 18:16:12 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:56112 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756523AbaIQWQK (ORCPT ); Wed, 17 Sep 2014 18:16:10 -0400 MIME-Version: 1.0 In-Reply-To: <541A045E.3030206@redhat.com> References: <1410325808-3657-1-git-send-email-ast@plumgrid.com> <1410325808-3657-13-git-send-email-ast@plumgrid.com> <54103776.3080706@redhat.com> <54193542.6080101@redhat.com> <541A045E.3030206@redhat.com> Date: Wed, 17 Sep 2014 15:16:08 -0700 Message-ID: Subject: Re: [PATCH v11 net-next 12/12] bpf: mini eBPF library, test stubs and verifier testsuite From: Alexei Starovoitov To: Daniel Borkmann Cc: "David S. Miller" , Ingo Molnar , Linus Torvalds , Andy Lutomirski , Steven Rostedt , Hannes Frederic Sowa , Chema Gonzalez , Eric Dumazet , Peter Zijlstra , Pablo Neira Ayuso , "H. Peter Anvin" , Andrew Morton , Kees Cook , Linux API , Network Development , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 17, 2014 at 2:59 PM, Daniel Borkmann wrote: >> >> 3. >> kernel/bpf/test_stubs.c can be removed once real tracing >> or socket use case is in. > > > Yes, please, lets go for point 3 at the very least. agree. test_stubs is a way to have verifier testsuite as the first ebpf user in this patch set. There are multiple ways of connecting ebpf to tracing/sockets and these discussions cannot happen all at once. So test_stubs to some degree is scaffolding to bring other pieces in place slowly with required due diligence. I don't think there will be a need for test_stubs when tracing+ebpf is in place. That's why I didn't introduce special prog_type and map_type for it and instead used 'unspec' type which is invalid type and used for testing temporarily. verifier testsuite, of course, will stay. It will switch from 'unspec' type to real types when they're ready.