[ltt-dev] Some LTTng 0.43 issue on ARM [Update]

Bryan Hsieh bryanhsieh at fihspec.com
Fri Jul 31 06:07:20 EDT 2009


Hi Mathieu, all,

I update some status with [update] [/update] notation below, Thanks!

I've ported LTTng 0.43 on Android successfully, but I am wondering if the result is correct, please help me to verify, thank you very much!

My Traced machine:
ARM11 (ARM1136J(F)-S) / Linux 2.6.27 (Android 1.5)
My visualization machine:
X86 / Sun xVM Virtual Box (Unbuntu 8.10)

LTTng: 0.43
LTTV: 0.11.2
LTT Control: 0.55

I connect to Android shell by ADB tool after Android bring up, then I command as following step, the command line options are different with LTTng manual, because the example in manual is for old version.

# ltt-armall
Connecting all markers
Connecting high-rate markers to tap
# lttctl -n trace1 -d -l /sys/kernel/debug/ltt -t /system/tmp/trace1
Linux Trace Toolkit Trace Control 0.55-16102008

Controlling trace : trace1

Linux Trace Toolkit Trace Daemon 0.55-16102008

Reading from debugfs directory : /sys/kernel/debug/ltt/trace1
Writing to trace directory : /system/tmp/trace1

[update]
It seems the LTT control and daemon work fine. I run some scenarios for 1 minute on Android, but the trace files are still empty (all files length are 0)
What's wrong? Is there any step I missed? Or the LTT control and daemon don't work?

# ls -l  ../../sys/kernel/debug/ltt/
drwxr-xr-x root     root              1980-01-07 01:13 trace1
# ls -l  ../../sys/kernel/debug/ltt/trace1
-r-------- root     root            0 1980-01-07 01:13 cpu_0
drwxr-xr-x root     root              1980-01-07 01:13 control
# ls -l  ../../sys/kernel/debug/ltt/trace1/control
-r-------- root     root            0 1980-01-07 01:13 network_0
-r-------- root     root            0 1980-01-07 01:13 modules_0
-r-------- root     root            0 1980-01-07 01:13 processes_0
-r-------- root     root            0 1980-01-07 01:13 interrupts_0
-r-------- root     root            0 1980-01-07 01:13 metadata_0
# ls -l ../traces/
drwxrwxrwx root     root              1980-01-07 01:13 trace1
# ls -l ../traces/trace1
drwxrwxrwx root     root              1980-01-07 01:13 control
-rwxrwxrwx root     root            0 1980-01-07 01:13 cpu_0
# ls -l ../traces/trace1/control
-rwxrwxrwx root     root            0 1980-01-07 01:13 metadata_0
-rwxrwxrwx root     root            0 1980-01-07 01:13 interrupts_0
-rwxrwxrwx root     root            0 1980-01-07 01:13 processes_0
-rwxrwxrwx root     root            0 1980-01-07 01:13 modules_0
-rwxrwxrwx root     root            0 1980-01-07 01:13 network_0

>>> do something on Android

# lttctl -n trace1 -q
Linux Trace Toolkit Trace Control 0.55-16102008

Controlling trace : trace1

# lttctl -n trace1 -r
Linux Trace Toolkit Trace Control 0.55-16102008

Controlling trace : trace1

>>> Android shell hang in here, I have to press Ctrl+Z to force stopping - lttctl -n trace1 -r   .Why?  Is anything wrong?

# ls -l  ../../sys/kernel/debug/ltt/trace1
-r-------- root     root            0 1980-01-07 06:37 cpu_0
drwxr-xr-x root     root              1980-01-07 06:37 control
# ls -l  ../../sys/kernel/debug/ltt/trace1/control
-r-------- root     root            0 1980-01-07 06:37 network_0
-r-------- root     root            0 1980-01-07 06:37 modules_0
-r-------- root     root            0 1980-01-07 06:37 processes_0
-r-------- root     root            0 1980-01-07 06:37 interrupts_0
-r-------- root     root            0 1980-01-07 06:37 metadata_0
# ls -l  ../tmp/trace1
drwxrwxrwx root     root              1980-01-07 06:37 control
-rwxrwxrwx root     root      1048576 1980-01-07 06:37 cpu_0
# ls -l  ../tmp/trace1/control
-rwxrwxrwx root     root            0 1980-01-07 06:37 metadata_0
-rwxrwxrwx root     root            0 1980-01-07 06:37 interrupts_0
-rwxrwxrwx root     root        10240 1980-01-07 06:37 processes_0
-rwxrwxrwx root     root        65536 1980-01-07 06:37 modules_0
-rwxrwxrwx root     root        65536 1980-01-07 06:37 network_0

The Channel in /sys/kernel/debug/ltt/trace1 is clear.  Does it cause by destroy channel command?
The metadata_0 and interrupts_0 are empty, Is that correct? I've done some key press, the interrupts_o shouldn't be empt.
[/update]

BTW, I would like to know what is the channel concept for LTTng? What's the relationship between trace and channel? What's the normal, flight recorder and hybrid mode? So far, I can't find related document or the information isn't enough for me.
Which files should I get for LTTV on another visualization machine?
[update]
As The LTTng trace format document description, I assume I just only need to put the /tmp/trace1 directory tree in visualization machine and command LTTV below. Is that right?
Lttv -m textDump -t /tmp/trace1
[/update]

Thanks for your help!

Best regards,
Bryan Hsieh
SPEC, FIH Co., Ltd.
Tel:+886-3-270-0000 #2723
Fax:+886-3-270-0001


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090731/9bfe4548/attachment-0003.htm>


More information about the lttng-dev mailing list