From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Rostedt Subject: Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events Date: Mon, 5 Feb 2018 10:10:11 -0500 Message-ID: <20180205101011.720f9493@gandalf.local.home> References: <20180202230458.840252014@goodmis.org> <261141691.15507.1517677454208.JavaMail.zimbra@efficios.com> <292744194.15823.1517758204087.JavaMail.zimbra@efficios.com> <20180205100930.GH2249@hirez.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Mathieu Desnoyers , linux-kernel , Ingo Molnar , Andrew Morton , Thomas Gleixner , Masami Hiramatsu , Tom Zanussi , linux-rt-users , linux-trace-users , acme , Clark Williams , Jiri Olsa , bristot , Juri Lelli , Jonathan Corbet , Namhyung Kim , Alexei Starovoitov To: Peter Zijlstra Return-path: In-Reply-To: <20180205100930.GH2249@hirez.programming.kicks-ass.net> Sender: linux-trace-users-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org On Mon, 5 Feb 2018 11:09:31 +0100 Peter Zijlstra wrote: > As a run-around, Steve then suggested to decouple the trace-hook from > the actual trace-event. Let the scheduler only provide the hook, nothing > else. And then allow users to create their own events with the specific > data they need for their specific use-case. Actually, we can make the raw tracepoint callback no longer 'notrace', and then we can extend all tracepoints as well with this. One issue I hit was the structure randomization for security. If the structures are randomized, it becomes much more difficult to find specific aspects of task_struct. -- Steve