Hi Ajit,
I appreciate your reply!
But there is a problem here.
My installation of Busybox is 1.12.4.
I follow your suggestion to test on x86 Desktop ARM simulator, the message said that can't find /proc/ltt. I think it should be, because I didn't patch to ARM simulator Linux kernel.
[sbox-ARM: ~/ltt-control-0.55-16102008/lttctl] > ltt-armall
Connecting all markers
cat: /proc/ltt: No such file or directory
Connecting high-rate markers to tap
cat: /proc/ltt: No such file or directory
It should be work on my target device, but it seems not.
I can't find /ltt under /proc
Maybe it's root cause, but why there is no /ltt/proc? And why there is no " cat: /proc/ltt: No such file or directory" message in my target device during running ltt-armall?
BTW, I mount debugfs in init.c
Mount("debugfs", "/sys/kernel/debug", "debugfs", 0, NULL);
It should not be a problem.
-----------------------------------------------------------------------------------------------------------Another problem:
I command as following steps.
# 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 ../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.
And those files almost filled by 0 except for the short header I can't make sure, it looks like incomplete.
I hope you can help me to solve these issues, I am appreciate you so much.
Best regards,
Bryan Hsieh
SPEC, FIH Co., Ltd.
Tel:+886-3-270-0000 #2723
Fax:+886-3-270-0001
-----Original Message-----
From: Ajit R [mailto:ajitrzid at yahoo.com]
Sent: Friday, July 31, 2009 6:17 PM
To: 'ltt-dev at lists.casi.polymtl.ca'; Bryan Hsieh
Cc: Tommy Peng
Subject: Re: [ltt-dev] Some LTTng 0.43 issue on ARM
Hi Bryan,
My replies with the [Ajit] tag.
LTT Gods correct me if I am wrong.
Thanks
Ajit
--- On Fri, 7/31/09, Bryan Hsieh <bryanhsieh at fihspec.com> wrote:
> From: Bryan Hsieh <bryanhsieh at fihspec.com>
> Subject: [ltt-dev] Some LTTng 0.43 issue on ARM
> To: "'ltt-dev at lists.casi.polymtl.ca'" <ltt-dev at lists.casi.polymtl.ca>
> Cc: "Tommy Peng" <tommypeng at fihspec.com>
> Date: Friday, July 31, 2009, 12:19 PM
> Hi Mathieu,
> all,
>
>
>
>
> 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
>
[ Ajit ]
ltt-armall is a shell script. It connects + arms the markers in the
kernel. So depending on your kernel + LTT version it would write some
"text" into the /proc/ltt directory or a "1" into files in
the debugfs directory.
Make sure, the binaries for running the script are available in your target environment. For eg. awk, grep, sed etc. Busybox versions might have their limitations. If they do not work, you could do equivalent things on your Desktop and then write a simple script, doing the same on your target.
Once you run "ltt-armall", you should see some debug statements in your "dmesg" like "connect" or "arm" etc.
>
> Connecting all
> markers
>
> Connecting high-rate
> markers to tap
>
> # lttctl
> -n trace1 -d -l /sys/kernel/debug/ltt -t
> /system/traces/trace1
>
[Ajit]
Not sure if your "-l" option is right. you have to point it to the place where you mounted your debugfs.
>
> 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/traces/trace1
>
>
>
>
> 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
>
[Ajit]
If you have connected and armed it right, you should see the cpu_0
file increasing in size. After sometime, disconnect by running the
ltt-control -n whatever-name -R
and then you will see files in the control directory (network, process, etc ) grown in size. Tar and move the trace directory to your host and do the needful.
> 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
>
>
>
>
> 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?
>
> Which
> files should I get
> for LTTV on another visualization
> machine?
>
> So far, I
> can't find related document or the
> information isn't enough for me.
>
>
>
>
> Thanks for your
> help!
>
>
>
>
> Best
> regards,
>
> Bryan Hsieh
>
> SPEC, FIH
> Co., Ltd.
>
> Tel:+886-3-270-0000 #2723
>
> Fax:+886-3-270-0001
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
This e-mail message together with any attachments thereto (if any) is confidential, protected under an enforceable non-disclosure agreement,
intended only for the use of the named recipient(s) above and may contain information that is privileged, belonging to professional work products
or exempt from disclosure under applicable laws. Any unauthorized review, use, copying, disclosure, or distribution of any information contained
in or attached to this transmission is STRICTLY PROHIBITED and may be against the laws. If you have received this message in error, or are not
the named recipient(s), please immediately notify the sender by e-mail or telephone at IT support hotline 886-3-2700000 EXT 1333 and delete this
e-mail message and any attached documentation from your computer. Receipt by anyone other than the intended recipient(s) is not a waiver of any
attorney-client or work product privilege. Thank you!