This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Getting started: trying to build a kernel tracing tool for viewing assembly code
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "Dan Connors" <dconnors at colorado dot edu>
- Cc: systemtap at sources dot redhat dot com
- Date: 12 Jul 2007 15:42:31 -0400
- Subject: Re: Getting started: trying to build a kernel tracing tool for viewing assembly code
- References: <7ee18c180707120837r701e6d5br38e6f87b412301ff@mail.gmail.com> <7ee18c180707121024o4f42dd3y8e3be61bfe7b6cb4@mail.gmail.com>
"Dan Connors" <dconnors@colorado.edu> writes:
> I'm just getting started with SystemTap: trying to build a kernel
> tracing tool for viewing assembly code as well as memory addresses.
> [...]
I am not sure what that means. If it's wanting to get a trace of all
kernel instructions, then it may be useful to look at the IBM itrace
system. Considering the huge performance penalty that per-instruction
tracing is bound to cause, it may be worthwhile to run your whole
kernel under a simulator, and instrument that rather than the kernel
running underneath.
- FChE