From: Jiri Olsa <jolsa@redhat.com>
To: Remi Bernon <rbernon@codeweavers.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jacek Caban <jacek@codeweavers.com>
Subject: Re: [PATCH 3/3] perf tests: Add test for PE binary format support
Date: Wed, 24 Jun 2020 15:10:39 +0200 [thread overview]
Message-ID: <20200624131039.GC2719003@krava> (raw)
In-Reply-To: <20200624103041.825746-3-rbernon@codeweavers.com>
On Wed, Jun 24, 2020 at 12:30:41PM +0200, Remi Bernon wrote:
> This adds a precompiled file in PE binary format, with split debug file,
> and tries to read its build_id and .gnu_debuglink sections, as well as
> looking up the main symbol from the debug file. This should succeed if
> libbfd is supported.
SNIP
> diff --git a/tools/perf/tests/pe-file.exe b/tools/perf/tests/pe-file.exe
> new file mode 100644
dreams coming true.. windows.exe file in perf sources ;-)
awesome, thanks for the test
jirka
prev parent reply other threads:[~2020-06-24 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 10:30 [PATCH 1/3] perf dso: Use libbfd to read build_id and .gnu_debuglink section Remi Bernon
2020-06-24 10:30 ` [PATCH 2/3] perf symbols: Try reading the symbol table with libbfd Remi Bernon
2020-06-24 13:25 ` Jiri Olsa
2020-06-24 13:40 ` Rémi Bernon
[not found] ` <32a0da28-aca7-34b0-adb2-b0f61021fba8@codeweavers.com>
2020-07-08 18:33 ` Jiri Olsa
2020-06-24 10:30 ` [PATCH 3/3] perf tests: Add test for PE binary format support Remi Bernon
2020-06-24 13:10 ` Jiri Olsa [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=20200624131039.GC2719003@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jacek@codeweavers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rbernon@codeweavers.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