[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADyE4xFEvoXQV_1qZy1O2RNbMsOCebYpnjNauMFVP6jfn9kNVw@mail.gmail.com>
Date: Tue, 3 Apr 2012 16:55:44 +0900
From: Masami Hiramatsu <masami.hiramatsu@...il.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
Huang Ying <ying.huang@...el.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Jason Wessel <jason.wessel@...driver.com>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC PATCH -tip 00/16] in-kernel x86 disassember
2012/4/3 H. Peter Anvin <hpa@...or.com>:
> On 04/02/2012 12:04 AM, Ingo Molnar wrote:
>> Perf could use
>> a programmatic, librarized disassembler for its assembly
>> annotation code.
>
> BTW, it should be pretty trivial to librarize the disassembler from
> NASM. Even more so, I think this might have already been done with Yasm.
Technically, yes. There are already many disassemblers. This series
was just started for my interesting of how disassember works and
helps kprobes debugging :)
Oh, and also, I'd like to try reusing x86-opcode-map.txt which is already
in the kernel tree. :)
Thank you,
--
Masami Hiramatsu
mailto:masami.hiramatsu@...il.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists