From: Peter Zijlstra <peterz@infradead.org>
To: Brian Robbins <brianrob@microsoft.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf: Fallback to JIT support for mmap'd non-ELF binaries.
Date: Thu, 19 Nov 2015 20:31:01 +0100 [thread overview]
Message-ID: <20151119193101.GQ3816@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1447960147-2681-1-git-send-email-brianrob@microsoft.com>
On Thu, Nov 19, 2015 at 11:09:07AM -0800, Brian Robbins wrote:
> Programs can execute code contained in files that don't conform
> to the ELF standard. This is common for cross-platform runtimes
> that support ahead-of-time compilation. In this case, perf is
> unable to resolve addresses to symbolic names, as the format of
> the mmap'd file is unknown to perf.
I'm assuming you're using PECOFF? Why not teach perf to read those?
Surely there's a library that can parse that stuff, it seems to me Wine
for one needs fairly decent support for this, also GDB (and other
toolchain bits) on Windows targets.
Its just that I was hoping we could move towards getting rid of those
/tmp files now that we have much better JIT support.
next prev parent reply other threads:[~2015-11-19 19:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 19:09 [PATCH] perf: Fallback to JIT support for mmap'd non-ELF binaries Brian Robbins
2015-11-19 19:31 ` Peter Zijlstra [this message]
2015-11-19 23:45 ` Brian Robbins
2015-11-20 0:09 ` Stephane Eranian
2015-11-20 18:36 ` Brian Robbins
2015-11-20 19:32 ` Peter Zijlstra
2015-11-20 21:18 ` Brian Robbins
2015-11-21 21:41 ` Arnaldo Carvalho de Melo
2015-11-23 17:36 ` Stephane Eranian
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=20151119193101.GQ3816@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=brianrob@microsoft.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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