From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753253AbeBEPOl (ORCPT ); Mon, 5 Feb 2018 10:14:41 -0500 Received: from mail.kernel.org ([198.145.29.99]:54532 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752919AbeBEPOd (ORCPT ); Mon, 5 Feb 2018 10:14:33 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3174D2075D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=mhiramat@kernel.org Date: Tue, 6 Feb 2018 00:14:28 +0900 From: Masami Hiramatsu To: Linus Torvalds Cc: Mathieu Desnoyers , rostedt , linux-kernel , 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 , Namhyung Kim , Alexei Starovoitov Subject: Re: [PATCH 00/18] [ANNOUNCE] Dynamically created function based events Message-Id: <20180206001428.baf7f16d4a836a17488d7248@kernel.org> In-Reply-To: References: <20180202230458.840252014@goodmis.org> <261141691.15507.1517677454208.JavaMail.zimbra@efficios.com> <292744194.15823.1517758204087.JavaMail.zimbra@efficios.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org (Note that I also agree with Linus's opinion that this is like a debugger, since I already did it in perf-probe :)) On Sun, 4 Feb 2018 11:39:39 -0800 Linus Torvalds wrote: > (Obviously it's not entirely black-and-white, but I do think there is > a pretty big difference between the two groups. And the first group > will obviously use the explicit trace points _too_, generally to > narrow down where they want to go with the function-based one). > > We'll see. Maybe I'm entirely wrong. But I'm hoping that the > function-based one will end up being helpful. BTW, if the function-based tracing is helpful for both of them, they can start using it back in 2010 because kprobe-based tracer already supported it. It was less announced, I must admit that I was lazy at that point. Also, since I moved usability effort on perf-probe, kprobe-based event syntax is not so funcy. "SyS_openat(int dfd, string path, x32 flags, x16 mode)" is equal to "p SyS_openat dfd=%di:x64 path=%si:string flags=%dx:x32 mode=%cx:x16" in kprobe probe definition syntax, but with perf-probe and CONFIG_DEBUG_INFO, perf probe -a 'sys_openat $params' will setup the event correctly. So, we need to clarify what will attract more "2nd group" people to function based events. E.g. the events for EXPORT_SYMBOL_GPL() symbols already defined and easily on/off. Thank you, -- Masami Hiramatsu