From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used Date: Thu, 12 Oct 2017 21:35:01 -0400 Message-ID: <20171012213501.17fe6f8c@vmware.local.home> References: <20171012184002.0661a867@gandalf.local.home> <20171013011450.w2uqygdfzwf7ud64@ast-mbp> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: LKML , Alexei Starovoitov , Daniel Borkmann , "David S. Miller" , netdev@vger.kernel.org To: Alexei Starovoitov Return-path: In-Reply-To: <20171013011450.w2uqygdfzwf7ud64@ast-mbp> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, 12 Oct 2017 18:14:52 -0700 Alexei Starovoitov wrote: > On Thu, Oct 12, 2017 at 06:40:02PM -0400, Steven Rostedt wrote: > > From: Steven Rostedt (VMware) > > > > All the trace events defined in include/trace/events/bpf.h are only > > used when CONFIG_BPF_SYSCALL is defined. But this file gets included by > > include/linux/bpf_trace.h which is included by the networking code with > > CREATE_TRACE_POINTS defined. > > > > If a trace event is created but not used it still has data structures > > and functions created for its use, even though nothing is using them. > > To not waste space, do not define the BPF trace events in bpf.h unless > > CONFIG_BPF_SYSCALL is defined. > > > > Signed-off-by: Steven Rostedt (VMware) > > Looks fine. > Acked-by: Alexei Starovoitov > > I'm assuming you want to take it through tracing tree along > with all other cleanups? Either way is fine. I have a few other ones. I believe Paul is taking the RCU patch. There's no dependency. I'll take it if it is easier for you. I just need the ack. -- Steve