linux-kernel - how to use perf annotate on the kernel

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTik2yNxwCHl7FZAyOG4Vt56RlLi59oZR5Jo6o9ox@mail.gmail.com>
Date:	Thu, 3 Jun 2010 19:23:02 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	linux-kernel@...r.kernel.org
Cc:	peterz@...radead.org, mingo@...e.hu, paulus@...ba.org,
	davem@...emloft.net, fweisbec@...il.com, acme@...radead.org,
	perfmon2-devel@...ts.sf.net, eranian@...il.com, eranian@...gle.com,
	tzanussi@...il.com
Subject: how to use perf annotate on the kernel

Arnaldo,

I am trying to understand how one is supposed
to use perf annotate to get sample correlations
with kernel symbols.

I do:

# perf record -a -e cycles:k dd if=/dev/zero of=/dev/null count=1000000
# perf report

# Events: 14K cycles
#
# Overhead          Command        Shared Object  Symbol
# ........  ...............  ...................  ......
#
     8.76%               dd  [kernel.kallsyms]    [k] __lock_acquire
     7.49%               dd  [kernel.kallsyms]    [k] sched_clock
     6.41%               dd  [kernel.kallsyms]    [k] __clear_user
     5.50%               dd  [kernel.kallsyms]    [k] sched_clock_local
     3.86%               dd  [kernel.kallsyms]    [k] cpu_clock
     3.82%               dd  [kernel.kallsyms]    [k] trace_hardirqs_off_caller
     3.50%               dd  [kernel.kallsyms]    [k] lock_release
     3.27%               dd  [kernel.kallsyms]    [k] system_call_after_swapgs
     3.15%               dd  [kernel.kallsyms]    [k] system_call

# perf annotate (or annotate -d '[kernel.kallsyms]'?)
Can't annotate __lock_acquire: No vmlinux file was found in the path

# perf annotate -k vmlinux
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file
objdump: '[kernel.kallsyms]': No such file

Am I missing something here?
Thanks.
--
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/