From: Paul Larson <plars@linuxtestproject.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: LTP - gettimeofday02 FAIL
Date: 18 Nov 2002 11:34:04 -0600 [thread overview]
Message-ID: <1037640849.21245.0.camel@plars> (raw)
In-Reply-To: <20021114215209.GA25778@tapu.f00f.org>
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
On Thu, 2002-11-14 at 15:52, Chris Wedgwood wrote:
> 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.
So this is a hardware issue? no way around this?
-Paul Larson
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-11-18 17:31 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
2002-11-18 17:34 ` Paul Larson [this message]
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=1037640849.21245.0.camel@plars \
--to=plars@linuxtestproject.org \
--cc=cw@f00f.org \
--cc=linux-kernel@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