From: David Miller <davem@davemloft.net>
To: acme@infradead.org
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, acme@redhat.com,
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 11:55:26 -0700 (PDT) [thread overview]
Message-ID: <20100315.115526.52182155.davem@davemloft.net> (raw)
In-Reply-To: <1268664418-28328-2-git-send-email-acme@infradead.org>
From: Arnaldo Carvalho de Melo <acme@infradead.org>
Date: Mon, 15 Mar 2010 11:46:58 -0300
> [root@doppio linux-2.6-tip]# perf top -s n_tty_write > /tmp/bla
> objdump: '[kernel.kallsyms]': No such file
>
> Now this is what the user gets:
>
> [root@doppio linux-2.6-tip]# perf top -s n_tty_write
> Can't annotate n_tty_write: No vmlinux file was found in the path:
> [0] vmlinux
> [1] /boot/vmlinux
> [2] /boot/vmlinux-2.6.33-rc5
> [3] /lib/modules/2.6.33-rc5/build/vmlinux
> [4] /usr/lib/debug/lib/modules/2.6.33-rc5/vmlinux
> [root@doppio linux-2.6-tip]#
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?
next prev parent reply other threads:[~2010-03-15 18:55 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 [this message]
2010-03-15 19:21 ` Arnaldo Carvalho de Melo
2010-03-15 19:26 ` David Miller
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.115526.52182155.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--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