From: ddaney@caviumnetworks.com (David Daney)
Subject: [ltt-dev] lttv unable to execute textDump on MIPS multicore target
Date: Mon, 14 Feb 2011 09:48:39 -0800 [thread overview]
Message-ID: <4D596AF7.9030607@caviumnetworks.com> (raw)
In-Reply-To: <BLU0-SMTP86B1C8A867AFBF486A0DEB96D00@phx.gbl>
On 02/14/2011 06:39 AM, Mathieu Desnoyers wrote:
> [ Adding David Daney to CC list, as he may have info on Octeon CPUs with
> non-synchronized TSCs ]
>
> * Naresh Bhat (nareshgbhat at gmail.com) wrote:
>> Hi Mathieu,
>>
>> I have backported the patch and now TSC is enabled in my kernel and also I
>> am able to boot the kernel. But one thing I have observed is between single
>> core and multiple core boot logs is that as following
>>
I missed the patch.
However, I would note that at the time I submitted my MIPS patches to
Mathieu, LTTng seemed to be working well on multi-CPU Octeon systems.
[...]
>
> timex.h:
>
> static inline void write_tsc(u32 val1, u32 val2)
> {
> #ifndef CONFIG_CPU_CAVIUM_OCTEON
> write_c0_count(val1);
> #else
> write_c0_cvmcount(((unsigned long) val2<< 32UL) | (unsigned long) val1);
> #endif
> /* Arrange for an interrupt in a short while */
> write_c0_compare(read_c0_count() + DELAY_INTERRUPT);
> }
>
This is not correct. The main clocksource as well as sched_clock()
which is used by ftrace and the scheduler are all driven by c0_cvmcount.
We take great care to properly synchronize this counter across all
CPUs when they are brought on-line. Anything that sets this counter can
only make the synchronization worse, not better.
David Daney
next prev parent reply other threads:[~2011-02-14 17:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 6:38 Naresh Bhat
2011-02-11 6:38 ` Naresh Bhat
2011-02-11 6:38 ` Naresh Bhat
2011-02-11 7:07 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP48F24DF0C4B7D6CF250B2696EF0@phx.gbl>
2011-02-11 7:30 ` Naresh Bhat
2011-02-11 7:30 ` Naresh Bhat
2011-02-11 7:30 ` Naresh Bhat
2011-02-11 14:26 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP19709C87A494AE8507C77296EF0@phx.gbl>
2011-02-14 8:48 ` Naresh Bhat
2011-02-14 8:48 ` Naresh Bhat
2011-02-14 8:48 ` Naresh Bhat
2011-02-14 14:39 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP86B1C8A867AFBF486A0DEB96D00@phx.gbl>
2011-02-14 17:48 ` David Daney [this message]
2011-02-14 19:43 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP381C9DC048B0AF55E0C00596D00@phx.gbl>
2011-02-14 19:50 ` David Daney
2011-02-14 19:56 ` Mathieu Desnoyers
[not found] ` <20110214195622.GA18825@Krystal>
2011-02-15 3:32 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP25F09381155A8E4CF8878B96D30@phx.gbl>
2011-02-15 13:30 ` Naresh Bhat
2011-02-15 13:30 ` Naresh Bhat
2011-02-15 13:30 ` Naresh Bhat
2011-02-15 14:05 ` Mathieu Desnoyers
2011-02-15 14:05 ` Naresh Bhat
2011-02-15 14:05 ` Naresh Bhat
2011-02-15 14:05 ` Naresh Bhat
2011-02-15 14:09 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP89B659A630D5B5735DB78696D30@phx.gbl>
2011-02-16 11:26 ` Naresh Bhat
2011-02-16 11:26 ` Naresh Bhat
2011-02-16 11:26 ` Naresh Bhat
2011-02-16 17:23 ` David Daney
2011-02-16 18:40 ` Mathieu Desnoyers
[not found] ` <BLU0-SMTP53396496DB856B47F531CC96D20@phx.gbl>
2011-02-16 19:03 ` Naresh Bhat
2011-02-16 19:03 ` Naresh Bhat
2011-02-16 19:03 ` Naresh Bhat
[not found] ` <AANLkTikbLY=HpDOUQYErk_CBgAd4NDJeL5otptRHT3Uj@mail.gmail.com>
[not found] ` <20110218145546.GA13022@Krystal>
2011-02-18 15:04 ` [ltt-dev] [RELEASE] LTTng 0.245 (mips fix) Mathieu Desnoyers
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=4D596AF7.9030607@caviumnetworks.com \
--to=ddaney@caviumnetworks.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