From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf top using /proc/kcore
Date: Mon, 14 Oct 2013 23:09:35 -0300 [thread overview]
Message-ID: <20131015020935.GB30662@ghostprotocols.net> (raw)
Hi Adrian,
While testing 'perf top -U' to reply a message in another thread
I noticed that ksm symbols appeared as '[kernel]', and only when I tried
'perf top -U -v' to look at the DSO long name I noticed that it was...
/proc/kcore.
Question is: since we have access to /proc/modules, can't we
parse that, as when we have access to vmlinux, and recreate the mmaps,
etc, and see:
[module] symbol
Instead of grouping everything into a single [kernel] bucket?
- Arnaldo
next reply other threads:[~2013-10-15 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 2:09 Arnaldo Carvalho de Melo [this message]
2013-10-15 6:13 ` perf top using /proc/kcore Adrian Hunter
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=20131015020935.GB30662@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
/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