From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: "Martin Liška" <mliska@suse.cz>,
a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: introduce new two options for objdump.
Date: Tue, 19 May 2015 11:33:00 -0300 [thread overview]
Message-ID: <20150519143300.GL13946@kernel.org> (raw)
In-Reply-To: <555B48E6.6000307@gmail.com>
Em Tue, May 19, 2015 at 08:29:58AM -0600, David Ahern escreveu:
> On 5/19/15 8:08 AM, Arnaldo Carvalho de Melo wrote:
> >Em Thu, Jan 29, 2015 at 02:03:46PM +0100, Martin Liška escreveu:
> >>Newly introduced options usedfull for off-box usage:
> > New useful options for off-box usage:
> >> --objdump-prefix: specify prefix to add to the absolute paths
> >> where objdump looks for source files.
> >> --objdump-prefix-strip: indicate how many initial directory names
> >> to strip off the hardwired absolute paths, passed to objdump.
> >> It has no effect without --objdump-prefix.
> >Does this, for instance, allows one looking at source code + assembly
> >with debuginfo packages? Is that a usecase you tested this against?
> >Anyway, sorry for the delay in processing this, fell thru the cracks ;-\
> >Can you please respin this on top of my current perf/core, at:
> >git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> Perhaps it should be generalized a bit? Right now we have symfs for the
> location of the tree for binaries. What about a srcfs for a source tree?
That is a good idea indeed.
- Arnaldo
next prev parent reply other threads:[~2015-05-19 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 13:03 Martin Liška
2015-05-19 14:08 ` Arnaldo Carvalho de Melo
2015-05-19 14:29 ` David Ahern
2015-05-19 14:33 ` Arnaldo Carvalho de Melo [this message]
2015-05-20 13:02 ` Martin Liška
2015-05-20 13:05 ` Arnaldo Carvalho de Melo
2015-06-01 11:10 ` Martin Liška
2015-06-01 12:54 ` Arnaldo Carvalho de Melo
2015-06-01 13:58 ` Martin Liška
2015-06-01 14:17 ` Arnaldo Carvalho de Melo
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=20150519143300.GL13946@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--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
Powered by JetHome