From: Chris Wedgwood <cw@f00f.org>
To: Paul Larson <plars@linuxtestproject.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: LTP - gettimeofday02 FAIL
Date: Thu, 14 Nov 2002 13:52:09 -0800 [thread overview]
Message-ID: <20021114215209.GA25778@tapu.f00f.org> (raw)
In-Reply-To: <1037139074.10626.37.camel@plars>
On Tue, Nov 12, 2002 at 04:11:14PM -0600, Paul Larson wrote:
I have not been able to reproduce this on a single processor machine
though.
Basically, all the test does is:
gettimeofday(&tv1, NULL);
while(!done) {
gettimeofday(&tv2, NULL);
FAIL if tv2 < tv1
tv1 = tv2;
}
Any ideas on what could be causing this?
The TSC's aren't synchronized between CPUs.
This is becoming more and more of a problem and in-escapable on some
hardware so I'm starting to wonder if assuming the TSCs are even
roughly synchronized *anywhere* is a good idea.
--cw
next prev parent reply other threads:[~2002-11-14 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 22:11 LTP - gettimeofday02 FAIL Paul Larson
2002-11-14 21:52 ` Chris Wedgwood [this message]
2002-11-18 17:34 ` Paul Larson
2002-11-18 21:58 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 1:27 Jim Houston
2002-11-19 12:03 ` Andi Kleen
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=20021114215209.GA25778@tapu.f00f.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@linuxtestproject.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