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 18:28:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805408@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805400@msgid-missing>
>>>>> On Mon, 29 Oct 2001 10:10:44 -0800, Jesse Barnes <jbarnes@sgi.com> said:
Jesse> Regarding glibc though: we really don't want to have a
Jesse> different version just for our systems, so I'd like to come
Jesse> up with a generic solution.
Oh, yes, I guess I wasn't quite clear in my response: the "ITC are
synchronous" flag needs to be exported to user level (probably through
a /proc file). glibc then reads that flag and if the ITCs are *not*
synchronous, it has two choices:
- if there is a driver for a fine-grained machine timer, it can
use it
- if no such driver exists, it will not be able to provide
fine grained time stamps
So, you'll have to define and implement a driver interface to your
machine timer (on SN1 its in the chipset, right?). If you want to go
ahead with this, you might want to take a look at the Intel multimedia
timer spec as well. I have my issues with that spec (it doesn't
provide sufficient alignment guarantees, in my opiniono), but
considering it should help in designing an interface that will be
useful not just for SGI machines, but for all "big" ia64 machines.
Jesse> Maybe an ia64 specific clock driver that glibc could map in
Jesse> to read synchronized clock info?
Yup. The driver interface needs to allow direct user-level access to
the fine grained timer. Though I'd say the interface should be able
to accommodate hardware that can't map the timer into user space.
--david
next prev parent reply other threads:[~2001-10-29 18:28 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
2001-10-29 18:10 ` Jesse Barnes
2001-10-29 18:28 ` David Mosberger [this message]
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-105590698805408@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