From: Andi Kleen <andi@firstfloor.org>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
systemtap-ml <systemtap@sources.redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jim Keniston <jkenisto@us.ibm.com>
Subject: Re: [PATCH -tip 0/4 V3] tracing: kprobe-based event tracer
Date: Wed, 01 Apr 2009 22:14:54 +0200 [thread overview]
Message-ID: <873acsm8qp.fsf@basil.nowhere.org> (raw)
In-Reply-To: <49D37584.50208@redhat.com> (Masami Hiramatsu's message of "Wed, 01 Apr 2009 10:09:08 -0400")
Masami Hiramatsu <mhiramat@redhat.com> writes:
>
> I agreed. Fortunately, Jim Keniston and I wrote an x86 instruction
> decoder :-) which has been made originally for uprobe andd kprobes
> jump-optimizer.
>
> https://www.redhat.com/archives/utrace-devel/2009-March/msg00031.html
An alternative would be to adapt the x86 interpreter in KVM.
I thought for some time that that one should be available in
a more generic form in a library.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-01 20:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 22:58 [PATCH -tip 0/4 V3] tracing: kprobe-based event tracer Masami Hiramatsu
2009-04-01 13:36 ` Ingo Molnar
2009-04-01 14:09 ` Masami Hiramatsu
2009-04-01 14:27 ` Ingo Molnar
2009-04-01 17:40 ` Masami Hiramatsu
2009-04-01 17:47 ` Ingo Molnar
2009-04-01 20:14 ` Andi Kleen [this message]
2009-04-01 20:51 ` Masami Hiramatsu
2009-04-01 22:15 ` Andi Kleen
2009-04-01 23:21 ` Masami Hiramatsu
2009-04-02 7:36 ` Andi Kleen
2009-04-02 15:49 ` 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=873acsm8qp.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=fweisbec@gmail.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.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