From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools: Support srccode output
Date: Tue, 9 May 2017 14:36:46 +0200 [thread overview]
Message-ID: <20170509123646.GB9983@krava> (raw)
In-Reply-To: <20170509120638.9454-1-andi@firstfloor.org>
On Tue, May 09, 2017 at 05:06:38AM -0700, Andi Kleen wrote:
SNIP
> |12 f2();
> 0000000000400525 insn: e8 cc ff ff ff # PRED
> f2:
> 00000000004004f6 insn: 55
> |5 {
> 00000000004004f7 insn: 48 89 e5
> 00000000004004fa insn: 8b 05 2c 0b 20 00
> |6 c = a / b;
>
> Not supported for callchains currently, would need some
> layout changes there.
>
> v2:
> Limit number of cached source files
> Delete bogus comment.
> Directly use the line number / file from the bfd lookup code
> Add prefix to source to make it easier to handle for scripts
> Avoid redundant listing of lines
> Fix include guard in srccode.h
> Use a hash table for the source lookup.
>
> v3:
> Remove prefix. Remove unwind_inlines.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
jirka
next prev parent reply other threads:[~2017-05-09 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 12:06 [PATCH] perf, tools: Support srccode output Andi Kleen
2017-05-09 12:36 ` Jiri Olsa [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-04 0:18 Andi Kleen
2018-12-05 12:28 ` Jiri Olsa
2018-12-05 16:54 ` Arnaldo Carvalho de Melo
2018-12-05 17:05 ` Jiri Olsa
2018-12-05 17:33 ` Andi Kleen
2018-12-05 22:15 ` Arnaldo Carvalho de Melo
2017-05-08 20:22 Andi Kleen
2017-05-09 9:05 ` Jiri Olsa
2017-05-09 9:06 ` Jiri Olsa
2017-05-05 23:00 Andi Kleen
2017-05-07 14:45 ` Jiri Olsa
2017-05-07 15:29 ` Andi Kleen
2017-05-07 14:45 ` 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=20170509123646.GB9983@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.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