From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH tip 0/9] tracing: attach eBPF programs to tracepoints/syscalls/kprobe Date: Wed, 21 Jan 2015 20:56:43 -0500 Message-ID: <20150121205643.4d8a3516@gandalf.local.home> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Alexei Starovoitov Cc: Namhyung Kim , Ingo Molnar , Arnaldo Carvalho de Melo , Jiri Olsa , "David S. Miller" , Daniel Borkmann , Hannes Frederic Sowa , Brendan Gregg , Linux API , Network Development , LKML List-Id: linux-api@vger.kernel.org On Wed, 21 Jan 2015 17:49:08 -0800 Alexei Starovoitov wrote: > > This also makes it keeping events in the soft-disabled state. > > I was never able to figure out the use case for soft-disabled state. > Probably historical before static_key was done. No, it's not historical at all. The "soft-disable" is a way to enable from any context. You can't enable a static key from NMI or interrupt context, but you can enable a "soft-disable" there. As you can enable or disable events from any function that the function tracer may trace, I needed a way to enable them (make the tracepoint active), but do nothing until something else turns them on. -- Steve