From: David Miller <davem@davemloft.net>
To: acme@infradead.org
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, fweisbec@gmail.com,
efault@gmx.de, a.p.zijlstra@chello.nl, paulus@samba.org
Subject: Re: [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing
Date: Mon, 15 Mar 2010 12:26:05 -0700 (PDT) [thread overview]
Message-ID: <20100315.122605.124976085.davem@davemloft.net> (raw)
In-Reply-To: <20100315192125.GL6965@ghostprotocols.net>
From: Arnaldo Carvalho de Melo <acme@infradead.org>
Date: Mon, 15 Mar 2010 16:21:26 -0300
> Em Mon, Mar 15, 2010 at 11:55:26AM -0700, David Miller escreveu:
>> Arnaldo, if perf top can use the kallsyms to do it's normal task, why
>> can't it use that for symbol annotations too? Isn't there enough
>> information available?
>
> Annotation is done by objdump -dS, that requires an executable file to
> do ASM annotation, and one with DWARF info for source code annotation.
> What we have with /proc/kallsyms is just the symtab.
Ok, I really think we should link with libopcodes or similar so we can
handle the simple assembler annotation case without requiring the
kernel image being available.
That's what I was trying to achieve when I sent you the report
:-)
next prev parent reply other threads:[~2010-03-15 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 14:46 [PATCH 1/2] perf record: Enable the enable_on_exec flag if record forks the target Arnaldo Carvalho de Melo
2010-03-15 14:46 ` [PATCH 2/2] perf top: Properly notify the user that vmlinux is missing Arnaldo Carvalho de Melo
2010-03-15 18:55 ` David Miller
2010-03-15 19:21 ` Arnaldo Carvalho de Melo
2010-03-15 19:26 ` David Miller [this message]
2010-03-16 9:46 ` Ingo Molnar
2010-03-16 9:51 ` David Miller
2010-03-16 9:55 ` Ingo Molnar
2010-03-16 9:58 ` David Miller
2010-03-15 15:15 ` [tip:perf/core] perf record: Enable the enable_on_exec flag if record forks the target tip-bot for Eric B Munson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100315.122605.124976085.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox