Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@polymtl.ca (Mathieu Desnoyers)
Subject: [ltt-dev] Steps to test LTTng on Linux-2.6.29 PowerPC
Date: Thu, 13 Aug 2009 10:26:39 -0400	[thread overview]
Message-ID: <20090813142639.GB32765@Krystal> (raw)
In-Reply-To: <6213bc560908130425lcd577e3n75570b7d1d35a245@mail.gmail.com>

* srikanth krishnakar (skrishnakar at gmail.com) wrote:
> 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:~#
> -------------------------------------------
> 

Don't forget to stop tracing before doing the textDump.

> 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 *
> 

Hm ? The gui environment works directly on the binary trace, not on a
text output.

> 
> 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 !!
> 

Just run:

lttv-gui /tmp/trace1

If you cannot run the GUI on your target machine, simply copy the
/tmp/trace1 directly to a different machine (can be powerpc, x86...) and
run lttv-gui from there.

Mathieu

> 
> Regards
> Srikanth Krishnakar
> **********************

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




      parent reply	other threads:[~2009-08-13 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 11:25 srikanth krishnakar
2009-08-13 11:25 ` srikanth krishnakar
2009-08-13 11:25 ` srikanth krishnakar
2009-08-13 14:26 ` Mathieu Desnoyers [this message]

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=20090813142639.GB32765@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    /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