public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] itc sync & clock_*
Date: Mon, 29 Oct 2001 15:54:13 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805404@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805400@msgid-missing>

>>>>> On Fri, 26 Oct 2001 10:09:47 -0700, Jesse Barnes <jbarnes@sgi.com> said:

  Jesse> David, you mentinoned awhile back that you don't expect the
  Jesse> itc counters to be synchronized in future machines and that
  Jesse> apps should use gettimeofday and the posix clock_* routines
  Jesse> to get timestamps.  However, the clock_* routines in recent
  Jesse> versions of glibc for ia64 look at ar.itc as the source of
  Jesse> clock tick information.  Does that need to be fixed?

Yes.  Uli knows about this.  It's just that we couldn't do anything
about it because there is no way of detecting this case.

  Jesse> This problem is more immediate on our hardware, as the clocks
  Jesse> are not synchronized, so I'd like to come up with a solution.
  Jesse> I'm not sure I understand all the issues yet, but I'd like to
  Jesse> solicit people for ideas and/or explaination about this
  Jesse> issue.

The first thing to do is to get this into the firmware.  Linux needs a
way to detect when the ITCs are not driven off the same clock (i.e.,
when there is a chance for the ITCs to drift).  There also needs to be
a way for detecting when the clock frequencies are different, but I
believe the info provided by PAL/SAL is sufficient (my only worry are
rounding errors...).

	--david


  reply	other threads:[~2001-10-29 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 17:09 [Linux-ia64] itc sync & clock_* Jesse Barnes
2001-10-29 15:54 ` David Mosberger [this message]
2001-10-29 18:10 ` Jesse Barnes
2001-10-29 18:28 ` David Mosberger
2001-10-29 18:33 ` Jack Steiner
2001-10-29 18:52 ` David Mosberger
2001-10-29 21:27 ` David Mosberger
2001-10-31 19:41 ` Jesse Barnes
2001-11-06  1:03 ` David Mosberger
2001-11-06  1:03 ` Jesse Barnes
2001-11-09  1:31 ` Mallick, Asit K
2001-11-09  2:06 ` David Mosberger

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=marc-linux-ia64-105590698805404@msgid-missing \
    --to=davidm@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