[ltt-dev] Steps to test LTTng on Linux-2.6.29 PowerPC

[skrishnakar@gmail.com (srikanth krishnakar)]

Hi Mathieu,

Arch: PowerPC

Just to re-write the steps for running the LTTng-0.65 for kernel
linux-2.6.29, please comments on the steps performed for tracing, or if any
modification required:

1. Create debugfs directory

$ mkdir /mnt/debugfs

2. Get the backup of fstab

$ cp /etc/fstab /etc/fstab.lttng.bkp

3. Write to /etc/fstab for automounting of debugfs

$ echo "debugfs   /mnt/debugfs  debugfs rw    0   0"  >> /etc/fstab


4.You can automate at boot time loading the ltt-control module by :

a.> Get the bakup of /etc/modules

$ cp /etc/modules /etc/modules.bkp

b.> Now execute the following :

echo ltt-trace-control >> /etc/modules
echo ltt-marker-control >> /etc/modules
echo ltt-tracer >> /etc/modules
echo ltt-serialize >> /etc/modules
echo ltt-relay >> /etc/modules
echo ipc-trace >> /etc/modules
echo kernel-trace >> /etc/modules
echo mm-trace >> /etc/modules
echo net-trace >> /etc/modules
echo fs-trace >> /etc/modules
echo jbd2-trace >> /etc/modules
echo ext4-trace >> /etc/modules
echo syscall-trace >> /etc/modules
echo trap-trace >> /etc/modules

----------------------------------------------------
Test modules loaded :

root at xilinx:~# lsmod
Module                  Size  Used by
ltt_serialize          11676  1 ltt_marker_control
ltt_marker_control      4932  1 ltt_trace_control
ltt_trace_control      16196  0
ipc_trace               2124  4
kernel_trace           14876  41
mm_trace                4892  12
net_trace               9116  23
fs_trace                5404  16
syscall_trace           1652  2
trap_trace              1628  2
root at xilinx:~#
-----------------------------------------------------

5.Now start tracing


>>> Before that don't forget to connect all the markers :

$ ltt-armall

.....................................................

Expected output:


t at xilinx:~# ltt-armall
Connecting all markers
Connecting /mnt/debugfs/ltt/markers/fs/buffer_wait_end
Connecting /mnt/debugfs/ltt/markers/fs/buffer_wait_start
Connecting /mnt/debugfs/ltt/markers/fs/close
Connecting /mnt/debugfs/ltt/markers/fs/exec
Connecting /mnt/debugfs/ltt/markers/fs/ioctl
Connecting /mnt/debugfs/ltt/markers/fs/llseek
Connecting /mnt/debugfs/ltt/markers/fs/lseek
Connecting /mnt/debugfs/ltt/markers/fs/open
Connecting /mnt/debugfs/ltt/markers/fs/pollfd
Connecting /mnt/debugfs/ltt/markers/fs/pread64
Connecting /mnt/debugfs/ltt/markers/fs/pwrite64
Connecting /mnt/debugfs/ltt/markers/fs/read
Connecting /mnt/debugfs/ltt/markers/fs/readv
Connecting /mnt/debugfs/ltt/markers/fs/select
Connecting /mnt/debugfs/ltt/markers/fs/write
Connecting /mnt/debugfs/ltt/markers/fs/writev
Connecting /mnt/debugfs/ltt/markers/input/input_event
.........
.........
.........
.........
* Truncated full log *
.....................................................


$ lttctl -C -w /tmp/trace1 trace1

-----------------------------------------

Expected output

root at xilinx:~# lttctl -C -w /tmp/trace1 trace1
Linux Trace Toolkit Trace Control 0.67-05032009

Controlling trace : trace1

lttctl: Creating trace
lttctl: Forking lttd
Linux Trace Toolkit Trace Daemon 0.67-05032009

Reading from debugfs directory : /mnt/debugfs/ltt/trace1
Writing to trace directory : /tmp/trace1

lttctl: Starting trace
root at xilinx:~#
-------------------------------------------

6. Dump output trace in text format:

$ lttv -m textDump -t /tmp/trace1  > Log-trace-text-format.txt

7. Dump output to a .lttng file for viewing in GUI environment :

$ lttv -m textDump -t /tmp/trace1 >* Lttng-out.lttng *


Please correct my steps, How can I create LTTng file that can be viewed
graphically (unlike earlier method of tracedump > $

lttv -m textDump -t tracedump > Lttng-out.lttng

)

How Can I get the tracedump for particular trace ?

Thanks in Advance !!


Regards
Srikanth Krishnakar
**********************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20090813/93b46997/attachment.htm>