Linux IA64 platform development
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: What contributes to IA64 ITC/TOD drift?
Date: Wed, 09 Feb 2005 19:53:30 +0000	[thread overview]
Message-ID: <16906.27194.372672.998370@napali.hpl.hp.com> (raw)
In-Reply-To: <AEBB9AF2F7713A4FAB1397435451162E01120E12@spock.invent.psi.com>

>>>>> On Tue, 8 Feb 2005 18:27:01 -0800, "John Lee" <jlee@platsolns.com> said:

  John> Maybe too broad a question but,

  John> 1. What in IA64 platform contributes to ITC drift?

Are you asking when the IA64_SAL_PLATFORM_FEATURE_ITC_DRIFT bit should
be set?  If so, then the answer is that it should be set whenever the
ITC clocks of the processors in a machine are not driven off the same
oscillator.

  John> 2. What in IA64 platform contributes to TOD fluctuation?
  John> (excluding the quality of oscillator)

NTP comes to mind.  Any other error I can think of probably would lead
to a systematic error, not to fluctuations.

	--david

  reply	other threads:[~2005-02-09 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  2:27 What contributes to IA64 ITC/TOD drift? John Lee
2005-02-09 19:53 ` David Mosberger [this message]
2005-02-09 22:25 ` John Lee

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=16906.27194.372672.998370@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