From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] UST - Problems in recording trace on a current process
Date: Mon, 15 Feb 2010 09:53:55 -0500 [thread overview]
Message-ID: <1266245635.1399.2.camel@Nokia-N900-42-11> (raw)
In-Reply-To: <19fa8ef31002150342v17a3755t99d255a9cc4ea011@mail.gmail.com>
----- Original message -----
> Hi Pierre,
>
> > > You could load in lttv both a userspace trace and a kernel trace that was
> > > recorded at the same time. You would then get appropriate events for
> drawing
> > > the CFV as well as userspace events. For that you would need to make sure
> the
> > > TSC clock is used in ust (see kernelcompat.h).
>
> I verified the clock source in kernelcompat.h. It uses gettimeofday from
> sys/time.h. As you suggested, its imperative that a tsc clock source is used
> when userspace and kernel tracing are combined.
>
> I went through the timesource patch of lttng,x86-trace-clock.patch, a patch
> dealing with switching clocksource of x86 architecture, to tsc.
>
> Can you suggest as to how we can change the clocksource to tsc in ust?
Just replace the time source function in kernelcompat.h with the one that is commented and that contains asm code to read the tsc.
>
> Regards,
> Naren
next prev parent reply other threads:[~2010-02-15 14:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:49 Naren
2010-02-08 21:49 ` Naren
2010-02-08 22:19 ` Pierre-Marc Fournier
[not found] ` <19fa8ef31002081428x1e215acfgd81d505ee359ce9@mail.gmail.com>
[not found] ` <201002081744.06912.pierre-marc.fournier@polymtl.ca>
2010-02-08 23:54 ` Naren
2010-02-08 23:54 ` Naren
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:37 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 1:48 ` soumyakanti chakraborty
2010-02-09 5:45 ` Pierre-Marc Fournier
2010-02-09 14:44 ` Naren
2010-02-09 14:44 ` Naren
2010-02-09 14:51 ` Douglas Santos
2010-02-09 14:51 ` Douglas Santos
2010-02-09 16:43 ` Naren
2010-02-09 16:43 ` Naren
2010-02-09 17:11 ` Pierre-Marc Fournier
2010-02-09 16:42 ` Pierre-Marc Fournier
2010-02-09 17:11 ` Naren
2010-02-09 17:11 ` Naren
2010-02-09 17:25 ` Pierre-Marc Fournier
2010-02-09 20:40 ` Naren
2010-02-09 20:40 ` Naren
2010-02-09 21:25 ` Douglas Santos
2010-02-09 21:28 ` Pierre-Marc Fournier
2010-02-10 0:50 ` Naren
2010-02-10 0:50 ` Naren
2010-02-10 15:26 ` Pierre-Marc Fournier
2010-02-10 16:53 ` Naren
2010-02-10 16:53 ` Naren
2010-02-10 20:15 ` Pierre-Marc Fournier
2010-02-10 22:08 ` Naren
2010-02-10 22:08 ` Naren
2010-02-12 0:18 ` Pierre-Marc Fournier
2010-02-12 9:10 ` Naren
2010-02-12 9:10 ` Naren
2010-02-15 6:04 ` Pierre-Marc Fournier
2010-02-15 6:23 ` Naveh, Ido
2010-02-15 12:16 ` Mathieu Desnoyers
2010-02-15 11:42 ` Naren
2010-02-15 11:42 ` Naren
2010-02-15 14:53 ` Pierre-Marc Fournier [this message]
2010-02-18 17:47 ` Pierre-Marc Fournier
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-18 22:58 ` Naren
2010-02-19 16:50 ` Pierre-Marc Fournier
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-19 17:15 ` Naren
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-22 0:46 ` soumyakanti chakraborty
2010-02-23 15:15 ` Pierre-Marc Fournier
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 1:55 ` soumyakanti chakraborty
2010-02-26 5:35 ` Pierre-Marc Fournier
2010-02-09 14:46 ` Douglas Santos
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=1266245635.1399.2.camel@Nokia-N900-42-11 \
--to=pierre-marc.fournier@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