From: Masami Hiramatsu <mhiramat@redhat.com>
To: Tim Abbott <tabbott@ksplice.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jim Keniston <jkenisto@us.ibm.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Anders Kaseorg <andersk@ksplice.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [RFC][ PATCH -tip 0/6] kprobes: Kprobes jump optimization support
Date: Wed, 17 Jun 2009 11:31:40 -0400 [thread overview]
Message-ID: <4A390C5C.9020606@redhat.com> (raw)
In-Reply-To: <4A381F8A.8020105@redhat.com>
Masami Hiramatsu wrote:
>> udis86 generates all its instruction table data from an XML opcode file,
>> which is I think what H. Peter Anvin was suggesting you should do in this
>> previous thread on your instruction decoder:
>> <http://lkml.indiana.edu/hypermail/linux/kernel/0904.0/01929.html>
>> Compared to e.g. libopcodes it is still quite small -- there's a total of
>> about 3000 lines of C, plus some instruction tables that are automatically
>> generated from an XML description of the instructions.
>
> I'm not so sure about udis86. Can I use it in exception path (and kprobes)?
> Is that XML things enough easy to be maintained?
And one big question is that who needs full featured disassembler in kernel.
It seems that kprobes and other potential user only need an instruction
decoder (and an instruction emulator too.)
Thank you,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-06-17 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 22:49 [RFC][ PATCH -tip 0/6] kprobes: Kprobes jump optimization support Masami Hiramatsu
2009-06-12 22:49 ` [RFC][ PATCH -tip 1/6] kprobes: use list instead of hlist for insn_pages Masami Hiramatsu
2009-06-12 22:49 ` [RFC][ PATCH -tip 2/6] kprobes: introducing generic insn_slot framework Masami Hiramatsu
2009-06-12 22:49 ` [RFC][ PATCH -tip 3/6] kprobes: kprobes jump optimization core Masami Hiramatsu
2009-06-12 22:49 ` [RFC][ PATCH -tip 4/6] kprobes: x86: cleanup save/restore registers Masami Hiramatsu
2009-06-12 22:49 ` [RFC][ PATCH -tip 5/6] kprobes: x86: support kprobes jump optimization on x86 Masami Hiramatsu
2009-06-12 22:50 ` [RFC][ PATCH -tip 6/6] kprobes: add documents of jump optimization Masami Hiramatsu
2009-06-16 19:50 ` [RFC][ PATCH -tip 0/6] kprobes: Kprobes jump optimization support Tim Abbott
2009-06-16 22:41 ` Masami Hiramatsu
2009-06-17 15:31 ` Masami Hiramatsu [this message]
2009-06-17 22:27 ` Masami Hiramatsu
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=4A390C5C.9020606@redhat.com \
--to=mhiramat@redhat.com \
--cc=ananth@in.ibm.com \
--cc=andersk@ksplice.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tabbott@ksplice.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