From: phyomh@gmail.com (Sam Liao)
Subject: [ltt-dev] Problem on combine kernel trace and userspace trace.
Date: Thu, 4 Nov 2010 14:22:56 +0800 [thread overview]
Message-ID: <AANLkTimDV-QwJq=ajSGoFcutThObTfab3k31zDRLAc14@mail.gmail.com> (raw)
In-Reply-To: <20101103151336.GA17967@Krystal>
On Wed, Nov 3, 2010 at 11:13 PM, Mathieu Desnoyers
<compudj at krystal.dyndns.org> wrote:
> * Sam Liao (phyomh at gmail.com) wrote:
>> Hi,
>>
>> I'm trying to combine the kernel trace and userspace trace, and it
>> seems that the
>> the userspace events can not be recognized to the right process with the kernel
>> events. I'm not sure if this is a problem of timestamp between kernel
>> and userspace.
>>
>> Here is the environment I'm using:
>> ----
>> Linux Trace Toolkit Visualizer 0.12.35-20082010
>> linux kernel 2.6.34.6
>> ust-0.4. ( I update the clock to use clock_gettime).
>
> If you are on x86 or powerpc, using the clock source that does not use
> clock_gettime would directly read the timestamp counter value, which
> should work. Make sure your architecture (on x86) has synchronized
> contant TSCs. LTTng complains about using a work-around in dmesg if it
> is not the case. If lttng uses the workaround on x86, then there is
> currently no mean to gather synchronized ust-lttng traces. As Julien
> said, we're currently working on a vdso solution to make this all work.
>
Thanks, after apply with the "rdtsc" clock source and set up the correct
clock frequency, the kernel trace and ust trace seems to be consistent
now.
Thanks,
-Sam
> Thanks,
>
> Mathieu
>
>> ----
>>
>> Is there anything I missed? Also I'm thinking about one problem, if
>> ust using clock_gettime to
>> get the nonseconds timestamp which is actually the timestamp that the user
>> application is doing the clock_gettime system call instead the
>> userspace event, how ust
>> deal with such difference and get this fixed when trace combination?
>>
>> Thanks,
>> -Sam
>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>>
>
> --
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
>
prev parent reply other threads:[~2010-11-04 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 9:24 Sam Liao
2010-11-03 14:04 ` Julien Desfossez
2010-11-03 15:03 ` Sam Liao
2010-11-03 15:13 ` Mathieu Desnoyers
2010-11-04 6:22 ` Sam Liao [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='AANLkTimDV-QwJq=ajSGoFcutThObTfab3k31zDRLAc14@mail.gmail.com' \
--to=phyomh@gmail.com \
/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