public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jes Sorensen <jes@wildopensource.com>
Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com
Subject: Re: ia64 clock_gettime and HP_TIMING
Date: Wed, 10 Dec 2003 23:39:00 -0000	[thread overview]
Message-ID: <3FD7AABA.9040809@redhat.com> (raw)
In-Reply-To: <yq0he09rogb.fsf@wildopensource.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> +	    n = read (fd, buf, sizeof buf);
> +	    if (__builtin_expect (n, 1) > 0)
> +	      {
> +		if (buf[0] != '0')
> +		  __itc_drift_internal = 1;
> +		else
> +		  __itc_drift_internal = -1;

All the machines I have looked at (mostly tigers) have "0" in
/proc/sal/itc_drift.  I.e., the machines wouldn't use the itc which
cannot be correct since they all use it now without problems.

- -- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/16q62ijCOnn/RHQRAoXHAJ9owgaK0JvRHLZ8oNpOKwjJcQ6sBACgvqGL
4xAmN/mO53C3CyRKYLNhmlQ=
=rjbU
-----END PGP SIGNATURE-----

  reply	other threads:[~2003-12-10 23:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-12 15:35 Jes Sorensen
2003-11-12 18:00 ` Ulrich Drepper
2003-11-13  8:25   ` Jes Sorensen
2003-11-13  9:15     ` Ulrich Drepper
2003-11-13 13:27       ` Jes Sorensen
2003-11-13 22:54         ` David Mosberger
2003-11-13 23:26           ` Ulrich Drepper
2003-11-14  9:46           ` Jes Sorensen
2003-11-14 17:57             ` Ulrich Drepper
2003-12-01 15:56               ` Jes Sorensen
2003-12-10  9:57                 ` Jes Sorensen
2003-12-10 23:39                   ` Ulrich Drepper [this message]
2003-12-11 10:50                     ` Jes Sorensen
2003-12-11 19:29                       ` David Mosberger
2003-12-11 20:48                 ` Ulrich Drepper
2003-12-12  8:49                   ` Jes Sorensen
2003-11-17 23:39             ` 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=3FD7AABA.9040809@redhat.com \
    --to=drepper@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=jes@wildopensource.com \
    --cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).