Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-16 Thread Steven Rostedt
On Mon, 16 Oct 2017 21:11:06 +0100 (WEST) David Miller wrote: > From: Steven Rostedt > Date: Mon, 16 Oct 2017 16:01:25 -0400 > > > On Mon, 16 Oct 2017 20:54:34 +0100 (WEST) > > David Miller wrote: > > > >> Steven, I lost track of how this patch is being handled. > >> > >> Do you want me to

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-16 Thread David Miller
From: Steven Rostedt Date: Mon, 16 Oct 2017 16:01:25 -0400 > On Mon, 16 Oct 2017 20:54:34 +0100 (WEST) > David Miller wrote: > >> Steven, I lost track of how this patch is being handled. >> >> Do you want me to merge it via my net-next tree? > > If you want. I could take it too if you give me

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-16 Thread Steven Rostedt
On Mon, 16 Oct 2017 20:54:34 +0100 (WEST) David Miller wrote: > Steven, I lost track of how this patch is being handled. > > Do you want me to merge it via my net-next tree? If you want. I could take it too if you give me an ack. It's not dependent on any other changes so it doesn't matter whic

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-16 Thread David Miller
From: Steven Rostedt Date: Thu, 12 Oct 2017 18:40:02 -0400 > 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 netwo

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-12 Thread Steven Rostedt
On Thu, 12 Oct 2017 18:38:36 -0700 Alexei Starovoitov wrote: > actually just noticed that xdp tracepoints are not covered by ifdef. > They depend on bpf_syscall too. So probably makes sense to wrap > them together. > bpf tracepoints are not being actively worked on whereas xdp tracepoints > keep

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-12 Thread Alexei Starovoitov
On Thu, Oct 12, 2017 at 09:35:01PM -0400, Steven Rostedt wrote: > 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/ev

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-12 Thread Steven Rostedt
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

Re: [PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-12 Thread Alexei Starovoitov
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 ne

[PATCH] tracing: bpf: Hide bpf trace events when they are not used

2017-10-12 Thread Steven Rostedt
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 creat