From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: [PATCH V4 0/9] perf tools: kcore improvements
Date: Mon, 7 Oct 2013 09:50:09 +0300 [thread overview]
Message-ID: <1381128618-22721-1-git-send-email-adrian.hunter@intel.com> (raw)
Hi
Here are some improvements for using kcore (version 4). There are 3
improvements:
- validate that kcore matches the perf.data modules
- workaround objdump difficulties with kcore
- add kcore to the build-id cache
Changes in V4:
perf tools: fix path unpopulated in machine__create_modules()
Dropped because it has been applied
perf buildid-cache: add ability to add kcore to the cache
Tweaked Documentation/perf-buildid-cache.txt
perf tools: add ability to find kcore in build-id cache
Changed to check read access to /proc/kcore before
skipping the buildid cache
Changes in V3:
perf tools: workaround objdump difficulties with kcore
change strncpy to strlcpy
perf buildid-cache: add ability to add kcore to the cache
change strncpy to strlcpy
perf tools: add ability to find kcore in build-id cache
change strncpy to strlcpy
Changes in V2:
perf tools: fix buildid cache handling of kallsyms with kcore
Dropped because it has been applied
perf tools: fix path unpopulated in machine__create_modules()
Use 'modules' pointer
Adrian Hunter (9):
perf tools: make a separate function to parse /proc/modules
perf tools: validate kcore module addresses
perf tools: workaround objdump difficulties with kcore
perf tools: add map__find_other_map_symbol()
perf tools: fix annotate_browser__callq()
perf tools: find kcore symbols on other maps
perf tools: add copyfile_mode()
perf buildid-cache: add ability to add kcore to the cache
perf tools: add ability to find kcore in build-id cache
tools/perf/Documentation/perf-buildid-cache.txt | 13 +
tools/perf/builtin-buildid-cache.c | 146 +++++-
tools/perf/ui/browsers/annotate.c | 10 +-
tools/perf/util/annotate.c | 36 +-
tools/perf/util/machine.c | 67 +--
tools/perf/util/map.c | 27 ++
tools/perf/util/map.h | 2 +
tools/perf/util/symbol-elf.c | 579 ++++++++++++++++++++++++
tools/perf/util/symbol-minimal.c | 15 +
tools/perf/util/symbol.c | 440 +++++++++++++++---
tools/perf/util/symbol.h | 20 +
tools/perf/util/util.c | 18 +-
tools/perf/util/util.h | 1 +
13 files changed, 1240 insertions(+), 134 deletions(-)
Regards
Adrian
next reply other threads:[~2013-10-07 6:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 6:50 Adrian Hunter [this message]
2013-10-07 6:50 ` [PATCH V4 1/9] perf tools: make a separate function to parse /proc/modules Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 2/9] perf tools: validate kcore module addresses Adrian Hunter
2013-10-08 7:18 ` Namhyung Kim
2013-10-07 6:50 ` [PATCH V4 3/9] perf tools: workaround objdump difficulties with kcore Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 4/9] perf tools: add map__find_other_map_symbol() Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 5/9] perf tools: fix annotate_browser__callq() Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 6/9] perf tools: find kcore symbols on other maps Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 7/9] perf tools: add copyfile_mode() Adrian Hunter
2013-10-07 6:50 ` [PATCH V4 8/9] perf buildid-cache: add ability to add kcore to the cache Adrian Hunter
2013-10-08 7:41 ` Namhyung Kim
2013-10-08 8:05 ` Adrian Hunter
2013-10-08 8:34 ` Namhyung Kim
2013-10-07 6:50 ` [PATCH V4 9/9] perf tools: add ability to find kcore in build-id cache 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=1381128618-22721-1-git-send-email-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).