linux-kernel - Re: mailing list for trace users

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1253617179.7695.17.camel@twins>
Date:	Tue, 22 Sep 2009 12:59:39 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Avi Kivity <avi@...hat.com>
Cc:	rostedt@...dmis.org, LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Mike Galbraith <efault@....de>
Subject: Re: mailing list for trace users

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/