Linux Trace Toolkit Reference Manual | |||
---|---|---|---|
<<< Previous Page | Home | Up | Next Page >>> |
3.1 Probing the kernel
insmod tracer
Having done this, you should see a new entry in /proc/devices.
./createdev.sh
If you load/unload device drivers often, you may want to run this script prior
to starting a trace session since the trace driver's major number is allocated
dynamically and may vary depending on the number of other drivers who have had their
number allocated dynamically too.
3.2 Probing RTAI
If you've tried to do as prescribed above with an LTT patched RTAI system, then you noticed that you can't install the tracer. The system complains about unresolved symbols. This is because it's a little bit more complicated with RTAI.
insmod [rtai-location]/rtai/modules/rtai_trace
insmod tracer
Having done this, you should see a new entry in /proc/devices.
./createdev.sh
If you load/unload device drivers often, you may want to run this script prior to starting a trace session since the trace driver's major number is allocated dynamically and may vary depending on the number of other drivers who have had their number allocated dynamically too. You can now install the other RTAI modules and trace your system.
3.3 Recording the data
A trace begins when the trace daemon starts recording events. If you have followed all the previous steps, this is currently not the case. To start recording, do:
tracedaemon -tsT /dev/tracer ./out.trace ./out.proc
kill [daemon pid]Type ps if you don't know the daemon's PID.
<<< Previous Page | Home | Up | Next Page >>> |
Linux trace toolkit | Data acquisition |