From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: sched_clock - cont'd
Date: Fri, 04 Jun 2004 14:52:40 +0000 [thread overview]
Message-ID: <16576.36024.383196.931650@napali.hpl.hp.com> (raw)
In-Reply-To: <40C08A29.A46DF067@nospam.org>
>>>>> On Fri, 04 Jun 2004 16:41:45 +0200, Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org> said:
Zoltan> Oops: timer tick before it's due
Zoltan> (itc˜59824596,itm˜5985c2ef) Oops: timer tick before it's
Zoltan> due (itc˜59f75936,itm˜59f9ac37) Oops: timer tick before
Zoltan> it's due (itc˜5a6c6c40,itm˜5a6d957f) CPU 3: synchronized
Zoltan> ITC with CPU 0 (last diff -3 cycles, maxerr 494 cycles)
Zoltan> Once it is over, everything seems to be correct. E.g. I can
Zoltan> stress the system by compiling the kernel with "make -j100".
Zoltan> It's a 2.6.5 kernel. I'm sure the new "sched_clock" code is
Zoltan> O.K. I guess this modification has brought to light a hidden
Zoltan> bug in the initial CPU synchronization or timing set up
Zoltan> code. Have you ever seen a similar problem ?
No. sched_clock() has nothing to do with the timer-tick or
time-of-day, so the problem must be something else.
--david
next prev parent reply other threads:[~2004-06-04 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 14:41 sched_clock - cont'd Zoltan Menyhart
2004-06-04 14:52 ` David Mosberger [this message]
2004-06-04 16:51 ` David Mosberger
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=16576.36024.383196.931650@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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