Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755990AbZIVK7p (ORCPT ); Tue, 22 Sep 2009 06:59:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755860AbZIVK7o (ORCPT ); Tue, 22 Sep 2009 06:59:44 -0400 Received: from viefep19-int.chello.at ([62.179.121.39]:15491 "EHLO viefep19-int.chello.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754360AbZIVK7o (ORCPT ); Tue, 22 Sep 2009 06:59:44 -0400 X-SourceIP: 213.93.53.227 Subject: Re: mailing list for trace users From: Peter Zijlstra To: Avi Kivity Cc: rostedt@goodmis.org, LKML , Ingo Molnar , Mathieu Desnoyers , Frederic Weisbecker , Arnaldo Carvalho de Melo , Thomas Gleixner , Masami Hiramatsu , Mike Galbraith In-Reply-To: <4AB89520.2050900@redhat.com> References: <1253132182.20020.242.camel@gandalf.stny.rr.com> <4AB89520.2050900@redhat.com> Content-Type: text/plain Date: Tue, 22 Sep 2009 12:59:39 +0200 Message-Id: <1253617179.7695.17.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1591 Lines: 44 On Tue, 2009-09-22 at 12:13 +0300, Avi Kivity wrote: > > Yes please. Here's a question to start it off - how to I 'perf > annotate' a symbol in a module? > > $ perf report > # Samples: 68202 > # > # Overhead Command Shared Object Symbol > # ........ ............... ............. ...... > # > 84.17% qemu-system-x86 [kernel] [k] vmx_vcpu_run > [kvm_intel] > 4.28% qemu-system-x86 [kernel] [k] > kvm_arch_vcpu_ioctl_run > [kvm] > 0.88% qemu-system-x86 [kernel] [k] add_preempt_count > 0.75% qemu-system-x86 [kernel] [k] > _spin_unlock_irqrestore > 0.68% qemu-system-x86 [kernel] [k] _spin_lock_irq > > $ perf annotate -k ~avi/kvm/linux-2.6/vmlinux -m vmx_vcpu_run > Error: symbol 'vmx_vcpu_run' not present amongst the samples. > > builtin symbols work. We need a /proc/modules parser that then also locates and loads .ko files which aren't stripped. I think Mike played around with that a bit. The typical problem is that people use 'make INSTALL_MOD_STRIP=1 modules_install' to install their modules, because otherwise the initrd thingies explode, the side effect is that the !initrd modules are stripped too. Ideally initrd tools should strip whatever they stick in. Then again, ideally we'd not have any initrd and modules crap to begin with ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/