From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Avi Kivity <avi@redhat.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Jim Keniston <jkenisto@us.ibm.com>,
kvm@vger.kernel.org, systemtap-ml <systemtap@sources.redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer
Date: Fri, 3 Apr 2009 14:25:39 +0200 [thread overview]
Message-ID: <20090403122539.GC11935@one.firstfloor.org> (raw)
In-Reply-To: <20090403121202.GI31399@elte.hu>
> So ... we can do the library decoder for kprobes purposes, and
> someone versed in the KVM emulator can then combine the two.
The KVM (or rather Xen, that is where it comes from) decoder is already
a "library decoder". That is it does nearly everything
through callbacks, and if you don't want some functionality
you can nop the callbacks. Nearly because some some
direct KVM references have crept in recently (e.g. to vcpus),
but those could be probably removed again without too much effort.
There are not many of them.
Also doing another interpreter is a lot of work and a lot of testing,
so basing it on something that is already well tested is probably
a good idea.
-/dev/null/Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-03 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 17:24 [PATCH -tip 0/6 V4] tracing: kprobe-based event tracer Masami Hiramatsu
2009-04-03 11:26 ` Ingo Molnar
2009-04-03 11:32 ` Andi Kleen
2009-04-03 11:50 ` Avi Kivity
2009-04-03 12:12 ` Ingo Molnar
2009-04-03 12:17 ` Avi Kivity
2009-04-03 12:26 ` Ingo Molnar
2009-04-03 12:33 ` Avi Kivity
2009-04-03 13:16 ` Vegard Nossum
2009-04-03 13:40 ` Avi Kivity
2009-04-03 13:52 ` Masami Hiramatsu
2009-04-05 19:37 ` Pekka Paalanen
2009-04-06 7:53 ` Avi Kivity
2009-04-03 12:25 ` Andi Kleen [this message]
2009-04-03 14:21 ` Masami Hiramatsu
2009-04-03 14:23 ` Ingo Molnar
2009-04-03 16:55 ` Masami Hiramatsu
2009-04-03 17:59 ` Jim Keniston
2009-04-03 14:30 ` Avi Kivity
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=20090403122539.GC11935@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=avi@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=kvm@vger.kernel.org \
--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