From: Jiri Olsa <jolsa@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/4] perf tools: Back [vdso] DSO with real data
Date: Mon, 10 Sep 2012 18:50:15 +0200 [thread overview]
Message-ID: <1347295819-23177-1-git-send-email-jolsa@redhat.com> (raw)
hi,
this patchset adds data behind the [vdso] map as a special DSO.
This is helpful for dwarf unwind, because now we can unwind
samples taken from [vdso] map. Example output is given in
patch 4/4.
Patch 1/1 fixies separate issue.
Attached patches:
1/4 perf tools: Do backtrace post unwind only if we regs and stack were captured
2/4 perf tools: Add memdup function
3/4 perf dso: Make dsos__find function globally available
4/4 perf tools: Back [vdso] DSO with real data
thanks,
jirka
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
---
tools/perf/Makefile | 2 ++
tools/perf/builtin-buildid-cache.c | 3 ++-
tools/perf/util/header.c | 70 +++++++++++++++++++++++++++++++++++++++-----------------
tools/perf/util/header.h | 2 +-
tools/perf/util/include/linux/string.h | 2 ++
tools/perf/util/map.c | 12 +++++++---
tools/perf/util/session.c | 7 ++++++
tools/perf/util/string.c | 18 ++++++++++++++-
tools/perf/util/symbol.c | 2 +-
tools/perf/util/symbol.h | 1 +
tools/perf/util/vdso.c | 111 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tools/perf/util/vdso.h | 18 +++++++++++++++
12 files changed, 220 insertions(+), 28 deletions(-)
next reply other threads:[~2012-09-10 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 16:50 Jiri Olsa [this message]
2012-09-10 16:50 ` [PATCH 1/4] perf tools: Do backtrace post unwind only if we regs and stack were captured Jiri Olsa
2012-09-14 5:58 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-09-10 16:50 ` [PATCH 2/4] perf tools: Add memdup function Jiri Olsa
2012-09-14 5:59 ` [tip:perf/core] " tip-bot for Jiri Olsa
2012-09-10 16:50 ` [PATCH 3/4] perf dso: Make dsos__find function globally available Jiri Olsa
2012-09-14 6:00 ` [tip:perf/core] perf symbols: " tip-bot for Jiri Olsa
2012-09-10 16:50 ` [PATCH 4/4] perf tools: Back [vdso] DSO with real data Jiri Olsa
2012-09-10 16:56 ` Peter Zijlstra
2012-09-14 6:01 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=1347295819-23177-1-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--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
all inboxes | Powered by JetHome®