From: Ingo Molnar <mingo@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
David Ahern <dsahern@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rabin Vincent <rabin@rab.in>
Subject: Re: [PATCH 1/1] perf annotate: Fix fallback to unparsed disassembler line
Date: Mon, 9 Mar 2015 12:09:58 +0100 [thread overview]
Message-ID: <20150309110957.GA12201@gmail.com> (raw)
In-Reply-To: <1425582200-28125-2-git-send-email-acme@kernel.org>
* Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> [...]
>
> Further investigation is needed to figure out the nature of the
> objdump output change so as to make the parser grok it.
Btw., maybe someone finds this interesting: we could also (re-)use the
in-kernel disassembler (on x86 and any other architecture that might
have one), which used by live patching facilities (kprobes et al).
See arch/x86/lib/insn.c.
The 'visualization' bit is missing entirely: but it does a lot of the
hard work of knowing about the instruction format: it knows about
essentially all x86 instructions and is able to determine instruction
boundaries, and can decode immediate constants.
Using this in tools/perf/ would have the added advantage that we could
then use the dissasembly in kernel oops output (nice feature!) - plus
tooling folks would help us fix and extend the kernel's disassembler!
;-)
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-09 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 19:03 [GIT PULL 0/1] perf/urgent fix Arnaldo Carvalho de Melo
2015-03-05 19:03 ` [PATCH 1/1] perf annotate: Fix fallback to unparsed disassembler line Arnaldo Carvalho de Melo
2015-03-05 19:19 ` Rabin Vincent
2015-03-09 11:09 ` Ingo Molnar [this message]
2015-03-09 13:25 ` Arnaldo Carvalho de Melo
2015-03-05 19:33 ` [GIT PULL 0/1] perf/urgent fix Ingo Molnar
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=20150309110957.GA12201@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=rabin@rab.in \
/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