From: Jes Sorensen <jes@trained-monkey.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sources.redhat.com, davidm@hpl.hp.com
Subject: Re: ia64 clock_gettime and HP_TIMING
Date: Thu, 13 Nov 2003 13:27:00 -0000 [thread overview]
Message-ID: <yq0n0b01jqr.fsf@trained-monkey.org> (raw)
In-Reply-To: <3FB34B5A.2040209@redhat.com>
>>>>> "Ulrich" == Ulrich Drepper <drepper@redhat.com> writes:
Ulrich> Jes Sorensen wrote:
>> In that case we should simply not provide HP timing on ia64.
Ulrich> "Oh, I cannot provide a feature for the machines I'm using.
Ulrich> That means nobody must use it."
This is a general problem on a large number of ia64 machines. Relying
on the ITC in userland without checking /proc/sal/itc_drift first is
simply broken.
Ulrich> The HP clocks are extremely useful. They stay.
I am not saying that should go, I am just asking we come up with a
solution that means our binaries return an error rather return
unreliable data.
How do you feel about a solution where we add a runtime check against
/proc/sal/itc_drift and handle it appropriately within the HP_TIMING
macros?
Cheers,
Jes
next prev parent reply other threads:[~2003-11-13 13:27 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 [this message]
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
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=yq0n0b01jqr.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=davidm@hpl.hp.com \
--cc=drepper@redhat.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).