From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] provide /proc/sal/itc_drift through AUX?
Date: Thu, 20 Mar 2003 19:57:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705278@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705273@msgid-missing>
>>>>> On 19 Mar 2003 21:06:20 -0500, Jes Sorensen <jes@wildopensource.com> said:
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
David> Why do you need to export it if you just use a light-weight
David> gettimeofday()? The light-weight syscall can readily access
David> the ITC-drift info via kernel memory.
Jes> Let me get sure I understand you right here, you are suggesting
Jes> I add a new syscall to provide the info currently found in
Jes> /proc/sal/itc_drift? Right now it's just returning true/false
Jes> (1/0) as to whether the ITC drifts or not.
No, not at all. I was simply suggesting to always use gettimeofday().
The light-weight implementation of gettimeofday() runs in ~130 cycles,
which isn't much slower than what you could do in user-level.
Jes> what are you referring to by HPET?
HPET = High Precision Event Timer. See:
http://www.intel.com/labs/platcomp/hpet/hpetspec.htm
--david
next prev parent reply other threads:[~2003-03-20 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 21:39 [Linux-ia64] provide /proc/sal/itc_drift through AUX? Jes Sorensen
2003-03-19 23:54 ` David Mosberger
2003-03-20 2:06 ` Jes Sorensen
2003-03-20 19:57 ` David Mosberger [this message]
2003-03-20 23:55 ` Rich Altmaier
2003-03-21 0:43 ` David Mosberger
2003-03-21 2:04 ` Jes Sorensen
2003-03-21 17:49 ` Jes Sorensen
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-105590723705278@msgid-missing \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.