From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Fionn Behrens <fionn@unix-ag.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
george anzinger <george@mvista.com>
Subject: Re: System time warping around real time problem - please help
Date: Tue, 25 Mar 2003 22:11:51 -0500 [thread overview]
Message-ID: <3E811A77.3060604@nortelnetworks.com> (raw)
In-Reply-To: 1048637613.29944.17.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> If you are using amd76x_pm boot with "notsc", ditto for that matter
> on dual athlons with APM or ACPI in some cases. In fact I wish people
> would stop using the tsc for clock timing altogether. It simply doesn't
> work on a lot of modern systems
But its awfully nice for low-impact high-resolution timestamps.
Maybe someday hardware manufacturers will give us a monotonic GHz+ clock that is
synced across all cpus and is cheap to read...
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-03-26 3:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:32 System time warping around real time problem - please help Fionn Behrens
2003-03-25 17:07 ` Richard B. Johnson
2003-03-25 17:17 ` Tim Schmielau
2003-03-25 18:12 ` Fionn Behrens
2003-03-25 18:29 ` Richard B. Johnson
2003-03-25 21:16 ` Fionn Behrens
2003-03-25 22:14 ` george anzinger
2003-03-25 22:55 ` Fionn Behrens
2003-03-26 0:13 ` Alan Cox
2003-03-26 2:28 ` george anzinger
2003-03-26 14:38 ` Alan Cox
2003-03-26 16:12 ` george anzinger
2003-03-26 17:06 ` Richard B. Johnson
2003-03-26 18:12 ` george anzinger
2003-03-26 3:11 ` Chris Friesen [this message]
2003-03-26 14:35 ` Alan Cox
2003-03-26 10:48 ` Fionn Behrens
[not found] <20030325164014$031c@gated-at.bofh.it>
2003-03-26 9:31 ` Kay Diederichs
-- strict thread matches above, loose matches on Subject: below --
2003-04-03 13:22 Fionn Behrens
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=3E811A77.3060604@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fionn@unix-ag.org \
--cc=george@mvista.com \
--cc=linux-kernel@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