From mboxrd@z Thu Jan 1 00:00:00 1970 From: Namhyung Kim Subject: Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events Date: Sun, 4 Feb 2018 11:25:20 +0900 Message-ID: References: <20180202230458.840252014@goodmis.org> <261141691.15507.1517677454208.JavaMail.zimbra@efficios.com> <20180203140217.2382df69@gandalf.local.home> <20180203205207.mpob4w6eyehhg2ky@ast-mbp> <20180203161732.4a65c66b@gandalf.local.home> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Alexei Starovoitov , Mathieu Desnoyers , linux-kernel , Linus Torvalds , Ingo Molnar , Andrew Morton , Thomas Gleixner , Peter Zijlstra , Masami Hiramatsu , Tom Zanussi , linux-rt-users , linux-trace-users , acme , Clark Williams , Jiri Olsa , bristot , Juri Lelli , Jonathan Corbet To: Steven Rostedt Return-path: Received: from mail-wr0-f172.google.com ([209.85.128.172]:34902 "EHLO mail-wr0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750738AbeBDCZm (ORCPT ); Sat, 3 Feb 2018 21:25:42 -0500 In-Reply-To: <20180203161732.4a65c66b@gandalf.local.home> Sender: linux-rt-users-owner@vger.kernel.org List-ID: Hi Steve and Alexei, On Sun, Feb 4, 2018 at 6:17 AM, Steven Rostedt wrote: > On Sat, 3 Feb 2018 12:52:08 -0800 > Alexei Starovoitov wrote: > >> It's a user space job. > > BTW, I asked around at DevConf.cz, and nobody I talked with (besides > Arnaldo), have used eBPF. The "path to hello world" is quite high. This > interface is extremely simple to use, and one doesn't need to install > LLVM or other tools to interface with it. > > I used the analogy, that eBPF is like C, and this is like Bash. One is > much easier to get "Hello World!" out than the other. > > So personally, this is something I know I would use (note, I have > never used eBPF either). But if I'm the only one to use this > interface then I'll stop here (and not bother with the function graph > return interface). If others think this would be helpful, I would ask > them to speak up now. I'm interested in this. From my understanding, it's basically function tracing + filter + custom argument info, right? Supporting arguments with complex type could be error-prone. We need to prevent malfunctions by invalid inputs. Thanks, Namhyung