From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
"Liang, Kan" <kan.liang@intel.com>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v1 4/4] perf script: enable printing of branch stack
Date: Wed, 19 Aug 2015 16:32:21 -0700 [thread overview]
Message-ID: <20150819233221.GL4524@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBQz=bcTzP8y9_ZA3iy_4MeuOtuAOnWJENkER+w_MddpQg@mail.gmail.com>
> > Also it would be good to resolve the addresses to symbol + offset
>
> But then, that becomes harder to post-process or even read with long
> C++ signatures.
Ok. Maybe make it optional?
For many usages resolved addresses will be much more useful than raw.
Normall call stacks also do that.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
prev parent reply other threads:[~2015-08-19 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 8:38 [PATCH v1 0/4] perf: improve script and record for iregs and brstack Stephane Eranian
2015-08-19 8:38 ` [PATCH v1 1/4] perf script: enable printing of interrupted machine state Stephane Eranian
2015-08-19 8:38 ` [PATCH v1 2/4] perf/x86: add list of register names Stephane Eranian
2015-08-19 8:38 ` [PATCH v1 3/4] perf record: add ability to name registers to record Stephane Eranian
2015-08-20 11:18 ` Jiri Olsa
2015-08-20 20:02 ` Stephane Eranian
2015-08-19 8:38 ` [PATCH v1 4/4] perf script: enable printing of branch stack Stephane Eranian
2015-08-19 22:11 ` Andi Kleen
2015-08-19 22:20 ` Stephane Eranian
2015-08-19 23:32 ` Andi Kleen [this message]
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=20150819233221.GL4524@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome