From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
jolsa@kernel.org, namhyung@kernel.org,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools, report: Add support for srcfile sort key
Date: Sat, 8 Aug 2015 04:27:35 +0200 [thread overview]
Message-ID: <20150808022735.GC1747@two.firstfloor.org> (raw)
In-Reply-To: <20150808000215.GE3583@kernel.org>
On Fri, Aug 07, 2015 at 09:02:15PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Aug 07, 2015 at 08:51:45PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Fri, Aug 07, 2015 at 03:54:24PM -0700, Andi Kleen escreveu:
> > > From: Andi Kleen <ak@linux.intel.com>
> > >
> > > In some cases it's useful to characterize samples by file. This is useful
> > > to get a higher level categorization, for example to map cost to
> > > subsystems.
> > >
> > > Add a srcfile sort key to perf report. It builds on top of the existing
> > > srcline support.
> >
> > Applied
>
> Humm, holding this up a bit, further testing showed some oddities,
> fedora21, the width of the column is being limited to the lenght of the
> header
Yes I've seen that, I just use -w normally. It also happens with --sort
srcline. The column sizing code could probably be somewhat smarter and
always allow the last column to become as wide as needed. But that's
something that should be done separately; I don't think it belongs
into this patch.
> and there are some DWARF errors, have you noticed those?
No I didn't. Some generic issue, likely happening with srcline and
perhaps even objdump -S too. Find out with strace what file it is.
-Andi
next prev parent reply other threads:[~2015-08-08 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 22:54 [PATCH] perf, tools, report: Add support for srcfile sort key Andi Kleen
2015-08-07 23:51 ` Arnaldo Carvalho de Melo
2015-08-08 0:02 ` Arnaldo Carvalho de Melo
2015-08-08 2:27 ` Andi Kleen [this message]
2015-08-08 17:28 ` Arnaldo Carvalho de Melo
2015-08-09 3:30 ` Namhyung Kim
2015-08-09 16:03 ` Andi Kleen
2015-08-10 14:51 ` Arnaldo Carvalho de Melo
2015-08-10 16:12 ` Arnaldo Carvalho de Melo
2015-08-10 18:32 ` Arnaldo Carvalho de Melo
2015-08-10 20:37 ` Arnaldo Carvalho de Melo
2015-08-11 2:28 ` Namhyung Kim
2015-08-12 12:30 ` [tip:perf/core] perf " tip-bot for Andi Kleen
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=20150808022735.GC1747@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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