From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753481Ab2AQMMg (ORCPT ); Tue, 17 Jan 2012 07:12:36 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:58311 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753142Ab2AQMMf (ORCPT ); Tue, 17 Jan 2012 07:12:35 -0500 Date: Tue, 17 Jan 2012 13:11:59 +0100 From: Ingo Molnar To: Srikar Dronamraju Cc: Jiri Olsa , Arnaldo Carvalho de Melo , Peter Zijlstra , Linus Torvalds , Oleg Nesterov , Andrew Morton , LKML , Linux-mm , Andi Kleen , Christoph Hellwig , Steven Rostedt , Roland McGrath , Thomas Gleixner , Masami Hiramatsu , Arnaldo Carvalho de Melo , Anton Arapov , Ananth N Mavinakayanahalli , Jim Keniston , Stephen Rothwell Subject: Re: [PATCH v9 3.2 7/9] tracing: uprobes trace_event interface Message-ID: <20120117121159.GA4959@elte.hu> References: <20120110114821.17610.9188.sendpatchset@srdronam.in.ibm.com> <20120110114943.17610.28293.sendpatchset@srdronam.in.ibm.com> <20120116131137.GB5265@m.brq.redhat.com> <20120117092838.GB10397@elte.hu> <20120117102231.GB15447@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120117102231.GB15447@linux.vnet.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org A couple of 'perf probe' usability issues. When running it as unprivileged user right now it fails with: $ perf probe -x /lib64/libc.so.6 free Failed to open uprobe_events file: Permission denied That error message should reference the full file name in question, i.e. /sys/kernel/debug/tracing/uprobe_events - that way the user can make that file writable if it's secure to do that on that system. The other thing is the text that gets printed: $ perf probe --del free Remove event: probe_libc:free that's not how tools generally communicate - it should be something like: $ perf probe --del free Removed event: probe_libc:free Note the past tense - this tells the user that the action has been performed successfully. Likewise, 'perf probe --add' should talk in past tense as well, to indicate success. So it should say something like: $ perf probe -x /lib64/libc.so.6 free Added new event: probe_libc:free (on 0x7f080) You can now use it in all perf tools, such as: perf record -e probe_libc:free -aR sleep 1 (Also note the s/on/in change in the other text.) Thanks, Ingo