From: phyomh@gmail.com (Sam Liao)
Subject: [ltt-dev] Problem on combine kernel trace and userspace trace.
Date: Wed, 3 Nov 2010 17:24:24 +0800 [thread overview]
Message-ID: <AANLkTimhRqQEE3G2FNQ-w431rDE_CqY0N0fgqp3CdAgf@mail.gmail.com> (raw)
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).
----
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
next reply other threads:[~2010-11-03 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 9:24 Sam Liao [this message]
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
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=AANLkTimhRqQEE3G2FNQ-w431rDE_CqY0N0fgqp3CdAgf@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