From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753626Ab2AQMWM (ORCPT ); Tue, 17 Jan 2012 07:22:12 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:38844 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753097Ab2AQMWE (ORCPT ); Tue, 17 Jan 2012 07:22:04 -0500 Date: Tue, 17 Jan 2012 13:21:33 +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: <20120117122133.GB4959@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 Have you tried to use 'perf probe' to achieve any useful instrumentation on a real app? I just tried out the 'glibc:free' usecase and it's barely usable. Firstly, the recording very frequently produces overruns: $ perf record -e probe_libc:free -aR sleep 1 [ perf record: Woken up 169 times to write data ] [ perf record: Captured and wrote 89.674 MB perf.data (~3917919 samples) ] Warning:Processed 1349133 events and lost 1 chunks! Using -m 4096 made it work better. Adding -g for call-graph profiling caused 'perf report' to lock up: perf record -m 4096 -e probe_libc:free -agR sleep 1 perf report [ loops forever ] I've sent a testcase to Arnaldo separately. Note that perf report --stdio appears to work. Regular '-e cycles -g' works fine, so this is a uprobes specific bug. Thanks, Ingo