From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Mike Galbraith <efault@gmx.de>,
Namhyung Kim <namhyung@gmail.com>,
Paul Mackerras <paulus@samba.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH V6 0/8] perf tools: kcore improvements
Date: Thu, 10 Oct 2013 14:48:43 +0200 [thread overview]
Message-ID: <20131010124843.GM3081@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <874n8qyt3z.fsf@tassilo.jf.intel.com>
On Wed, Oct 09, 2013 at 03:30:56PM -0700, Andi Kleen wrote:
> Peter Zijlstra <peterz@infradead.org> writes:
>
> > On Wed, Oct 09, 2013 at 03:01:10PM +0300, Adrian Hunter wrote:
> >> - workaround objdump difficulties with kcore
> >
> > I've no idea, but given that've 'inlined' addr2line, should we also
> > consider polling in objdump -- or at least that subset of functionality
> > that we actually use?
>
> FWIW addr2line is just a straight forward BFD call.
>
> objdump is significantly more complex, a lot of it is outside BFD
> (including the full disassembler and all the logic for syncing
> the source files)
Oh, that's unfortunate, I was hoping most of that would indeed be in
some library form or other.
prev parent reply other threads:[~2013-10-10 12:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 12:01 [PATCH V6 0/8] perf tools: kcore improvements Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 1/8] perf tools: validate kcore module addresses Adrian Hunter
2013-10-15 5:33 ` [tip:perf/core] perf symbols: Validate " tip-bot for Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 2/8] perf tools: workaround objdump difficulties with kcore Adrian Hunter
2013-10-15 5:33 ` [tip:perf/core] perf symbols: Workaround " tip-bot for Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 3/8] perf tools: add map__find_other_map_symbol() Adrian Hunter
2013-10-11 13:41 ` Arnaldo Carvalho de Melo
2013-10-09 12:01 ` [PATCH V6 4/8] perf tools: fix annotate_browser__callq() Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 5/8] perf tools: find kcore symbols on other maps Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 6/8] perf tools: add copyfile_mode() Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 7/8] perf buildid-cache: add ability to add kcore to the cache Adrian Hunter
2013-10-09 12:01 ` [PATCH V6 8/8] perf tools: add ability to find kcore in build-id cache Adrian Hunter
2013-10-09 12:07 ` [PATCH V6 0/8] perf tools: kcore improvements Peter Zijlstra
2013-10-09 22:30 ` Andi Kleen
2013-10-10 12:48 ` Peter Zijlstra [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=20131010124843.GM3081@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.com \
--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