Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux/MIPS <linux@cthulhu.engr.sgi.com>
Subject: Re: kernel sources?
Date: Sun, 16 Jan 2000 02:20:45 +0100	[thread overview]
Message-ID: <20000116022045.C12714@uni-koblenz.de> (raw)
In-Reply-To: <005e01bf5f7d$fc1cf490$0ceca8c0@satanas.mips.com>

On Sat, Jan 15, 2000 at 06:28:40PM +0100, Kevin D. Kissell wrote:

> As Ralf says, it's very accurate *if* you have an accurate picture of
> the CPU's clock frequency.  The usual mechanism of measuring
> the progress of the count register against elapsed time on a TOD
> clock has been known to be inaccurate on some platforms due
> to skew between the visibility to software and the actual timing
> event, so be careful.

The only machine where we actually calibrate the CPU counter is the Indy
where due to a hardware bug we cannot use the external timers as source
of interrupts.

In fact the current Linux kernel would even panic if it ever would find
an Indy working as per spec ;-)

We could improve that meassurement by rounding to the nearest crystal
known to be used on IP22 CPU modules plus maybe add an eventual user /
xntpd suplied fudge factor for deviations of the exact crystal frequency.

  Ralf

  parent reply	other threads:[~2000-01-16  1:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-15 17:28 kernel sources? Kevin D. Kissell
2000-01-15 20:06 ` information on getting up to speed Richard Dubrawsk
2000-01-16  1:20 ` Ralf Baechle [this message]
2000-01-16 12:32 ` kernel sources? Geert Uytterhoeven
     [not found] <Pine.LNX.4.05.10001130944010.3492-100000@callisto.of.borg>
2000-01-13 16:03 ` Geert Uytterhoeven
2000-01-14 11:32   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2000-01-11  9:53 Geert Uytterhoeven
2000-01-11 18:47 ` Harald Koerfgen
2000-01-12  8:57   ` Geert Uytterhoeven
2000-01-13  0:20     ` Ralf Baechle
2000-01-12 16:19   ` Geert Uytterhoeven

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=20000116022045.C12714@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=geert@linux-m68k.org \
    --cc=kevink@mips.com \
    --cc=linux@cthulhu.engr.sgi.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