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 21:27:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805411@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805400@msgid-missing>
>>>>> On Mon, 29 Oct 2001 15:35:02 -0500, "WEI,DONG (HP-Roseville,ex1)" <dong_wei@am.exch.hp.com> said:
Dong> Right now I need a description of the proposed flag to be
Dong> included in the firmware architectural definition. The
Dong> description should also include where (hardware register, or
Dong> platform knowledge, etc.) firmware would get such information
Dong> as to determine whether to set or clear the flag.
As far as I'm concerned, there definitely needs to be a flag that
indicates whether the ITCs are guaranteed to operate in lockstep
(i.e., with zero drift among them). The flag would *not* indicate
that the ITC are necessarily synchronized when the OS is started, just
that if the OS synchronizes them, they'll be guaranteed to stay in
lockstep.
A secondary question is whether the flag should indicate whether the
ITCs all run at the same frequency. At the moment, I don't believe
this is a good idea, because frequency and drift are separate issues.
Plus I *think* we should be able to handle the frequency question with
PAL_FREQ_RATIOS and SAL_FREQ_BASE. But we need to verify this (the
issue is whether measurement problems might cause PAL report slightly
different frequencies for different ITCs, even when they're driven off
the same clock and are therefore really the same).
It would be good if someone else could take the lead on this because
otherwise (and I'm sorry if I sound like a broken record) it will have
to wait until the book is done (which will be another couple of weeks,
really... ;-).
--david
next prev parent reply other threads:[~2001-10-29 21:27 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
2001-10-29 18:33 ` Jack Steiner
2001-10-29 18:52 ` David Mosberger
2001-10-29 21:27 ` David Mosberger [this message]
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-105590698805411@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