From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>
Cc: Paul Larson <plars@linuxtestproject.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [LTP] Re: LTP - gettimeofday02 FAIL
Date: Tue, 19 Nov 2002 16:10:28 +0100 [thread overview]
Message-ID: <20021119151028.GA13979@wotan.suse.de> (raw)
In-Reply-To: <1037719651.12118.7.camel@irongate.swansea.linux.org.uk>
On Tue, Nov 19, 2002 at 03:27:31PM +0000, Alan Cox wrote:
> On Tue, 2002-11-19 at 14:24, Andi Kleen wrote:
> > It is very hard to solve properly and efficiently. When you search the
> > list archives you will find long threads about the problem
> > (search for "TSC" and gettimeofday and perhaps HPET or cyclone). Last one
> > was one or two weeks ago.
> >
> > The problem has been there always in some way in linux, now it is just
> > exposed in LTP because it tests for it.
>
> Dual ppro boxes normally run with a locked synchronous TSC clock. That
> suggests the newer code broke stuff. It may also be due to the bug in
It is because of the HZ=1000. See Jim Houston's mail on the same topic,
he analyzed the failure.
Basically the current code cannot handle missing ticks properly on SMP and with
the new 1ms tick it is much more likely that a timer interrupt gets lost.
-Andi
next prev parent reply other threads:[~2002-11-19 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211190127.gAJ1RWg11023@linux.local.suse.lists.linux.kernel>
[not found] ` <1037713044.24031.15.camel@plars.suse.lists.linux.kernel>
2002-11-19 14:24 ` [LTP] Re: LTP - gettimeofday02 FAIL Andi Kleen
2002-11-19 15:27 ` Alan Cox
2002-11-19 15:10 ` Andi Kleen [this message]
2002-11-19 16:12 ` Alan Cox
2002-11-19 15:46 ` Andi Kleen
2002-11-19 1:27 Jim Houston
2002-11-19 13:37 ` [LTP] " Paul Larson
2002-11-19 14:02 ` Dave Jones
2002-11-19 14:50 ` Paul Larson
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=20021119151028.GA13979@wotan.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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