From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New attempt at adding an disassembler to perf
Date: Thu, 19 Jan 2017 16:36:41 +0100 [thread overview]
Message-ID: <20170119153641.GA16038@krava> (raw)
In-Reply-To: <20170119014150.19218-1-andi@firstfloor.org>
On Wed, Jan 18, 2017 at 05:41:45PM -0800, Andi Kleen wrote:
> A native disassembler in perf is very useful, in particular with perf script to trace
> instruction streams, but also for other analysis. Previously I attempted
> to do this using the udis86 library, but that was rejected because:
> - udis86 was not maintained anymore and lacking recent instructions
> - udis86 is dynamically linked and gives a runtime dependency.
> Doing this needs a full disassembler, not just a decoder, so the existing
> instruction decoder cannot be used without major changes.
>
> This patchkit addresses these issues. Intel recently released an open source version
> of the XED disassembler library, which is used in many other Intel software.
> It is very well maintained, uptodate, and supports static linking, so there is no
> runtime dependency. This version adds XED support to perf, and uses it to implement
> assembler output in perf script. It also fixes a range of issues in the previous
> version, see the individual change logs.
>
> Available in
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git perf/xed-6
i dont see that...
[jolsa@krava perf]$ git branch -r | grep xed-
ak/perf/xed-3
ak/perf/xed-4
jirka
>
> v1: First post of XED version
> v2: Change probing to not be default and support XED_DIR. Other cleanups
> based on review.
> v3: Use FEATURE_FLAGS_BASIC for probing
>
> -Andi
next prev parent reply other threads:[~2017-01-19 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 1:41 New attempt at adding an disassembler to perf Andi Kleen
2017-01-19 1:41 ` [PATCH 1/5] perf, tools: Add probing for xed Andi Kleen
2017-01-19 1:41 ` [PATCH 2/5] perf, tools: Add one liner warning for disabled features Andi Kleen
2017-01-19 1:41 ` [PATCH 3/5] perf, tools: Add disassembler for x86 using the XED library Andi Kleen
2017-01-19 1:41 ` [PATCH 4/5] perf, tools, script: Add support for printing assembler Andi Kleen
2017-01-23 19:49 ` Arnaldo Carvalho de Melo
2017-01-23 19:55 ` Andi Kleen
2017-01-23 20:06 ` Arnaldo Carvalho de Melo
2017-01-19 1:41 ` [PATCH 5/5] perf, tools, script: Add brstackasm output for branch stacks Andi Kleen
2017-01-24 18:54 ` Arnaldo Carvalho de Melo
2017-01-19 15:36 ` Jiri Olsa [this message]
2017-01-19 16:54 ` New attempt at adding an disassembler to perf Andi Kleen
2017-01-20 13:22 ` Jiri Olsa
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 9:00 Andi Kleen
2017-01-08 14:21 ` Jiri Olsa
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=20170119153641.GA16038@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).