Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: hgu1972@gmail.com (Harald Gustafsson)
Subject: [ltt-dev] OMAP3/4 trace clock and lockdep tracing
Date: Wed, 6 Apr 2011 10:32:58 +0200	[thread overview]
Message-ID: <BANLkTimUruypGb9gi1DYJ-XmghZsPSvmpA@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP50EBA923E8F17BCC6A80BD96A50@phx.gbl>

2011/4/6 Mathieu Desnoyers <compudj at krystal.dyndns.org>:
> Hrm, I should probably do this, can you try this patch out ? Can you
> test it and report if it fixes your problem ?

Thanks it fixes the problem. I made the corresponding changes in my
architecture's trace-clock.h which is a copy & paste of the omap
version. So I assume this would also work for the OMAP.

Now I only have the clock mismatch between the cores to deal with,
lttv complains for threads that are inserted before they are forked
(range is 10 us - 10 ms mismatch depending on run). I think it is due
to that the cores enters/leaves WFI unsynced and hence runs on cycle
counter and 32kHz clock in a different pattern and I get some error
due to this.  So far I run cpufreq on performance to not introduce
even more uncertainty. Have you tried the code on a OMAP4?

Regards,
  Harald




  parent reply	other threads:[~2011-04-06  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  8:54 Harald Gustafsson
2011-04-06  2:58 ` Mathieu Desnoyers
     [not found] ` <BLU0-SMTP50EBA923E8F17BCC6A80BD96A50@phx.gbl>
2011-04-06  8:32   ` Harald Gustafsson [this message]
2011-04-06 16:42     ` Mathieu Desnoyers
     [not found]     ` <BLU0-SMTP92A8ACAB7C397862CBB76D96A50@phx.gbl>
2011-04-07 12:57       ` Harald Gustafsson
2011-04-07 16:47         ` Mathieu Desnoyers
     [not found]         ` <BLU0-SMTP86985EF8EEA9698CAE849E96A40@phx.gbl>
2011-04-08  8:55           ` Harald Gustafsson

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=BANLkTimUruypGb9gi1DYJ-XmghZsPSvmpA@mail.gmail.com \
    --to=hgu1972@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