From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [ltt-dev] Kernel and User Space tracers have different timestamp reference
Date: Fri, 26 Nov 2010 08:08:08 -0500 [thread overview]
Message-ID: <4CEFB138.6030409@polymtl.ca> (raw)
In-Reply-To: <20101126082453.4252.72312.launchpad@wampee.canonical.com>
Hi folks,
I've received this bug report about kernel/UST trace synchronization.
Anyone knows what's the status on this?
Thanks,
Alexandre
On 10-11-26 03:24 AM, Florent Boudet wrote:
> Hello,
>
> I am sorry to contact you directly instead of filling a bug, but it
> seems the option is disabled on the launchpad project...
>
> I have recorded userspace traces at the same time as kernel traces, and
> opened both with LTTv.
> Timestamp for userspace traces and timestamp for kernel traces have
> different origins, which make it difficult to analyze.
> I am not sure about the cause, this might be related to a GMT/localtime
> issue...
>
> Regards,
> Florent Boudet
next parent reply other threads:[~2010-11-26 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101126082453.4252.72312.launchpad@wampee.canonical.com>
2010-11-26 13:08 ` Alexandre Montplaisir [this message]
2010-11-26 13:32 ` Mathieu Desnoyers
2010-11-26 13:47 ` David Goulet
2010-11-29 22:43 ` florent boudet
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=4CEFB138.6030409@polymtl.ca \
--to=alexandre.montplaisir@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