From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Joel.Becker@oracle.com, "Martin J. Bligh" <mbligh@aracnet.com>,
wim.coekaerts@oracle.com
Subject: [RFC][PATCH] linux-2.5.64_monotonic-clock_A1
Date: 11 Mar 2003 11:39:22 -0800 [thread overview]
Message-ID: <1047411561.16614.684.camel@w-jstultz2.beaverton.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
All,
Here is the next rev of my monotonic-clock patch. This version uses
scaled math to avoid the costly 64 bit divide at interrupt time. Big
thanks to George Anzinger for the suggestion.
This patch, written with the advice of Joel Becker, addresses a problem
with the hangcheck-timer. The basic problem is that the hangcheck-timer
code (Required for Oracle) needs a accurate hard clock which can be used
to detect OS stalls (due to udelay() or pci bus hangs) that would cause
system time to skew (its sort of a sanity check that insures the
system's notion of time is accurate). However, currently they are using
get_cycles() to fetch the cpu's TSC register, thus this does not work on
systems w/o a synced TSC. As suggested by Andi Kleen (see thread here:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0302.0/1234.html ) I've
worked with Joel and others to implement the monotonic_clock()
interface.
This interface returns a unsigned long long representing the number of
nanoseconds that has passed since time_init().
Future plans to the interface include properly handling cpu_freq changes
and porting to the different arches.
Comments, suggestions and flames welcome.
thanks
-john
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2003-03-11 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 19:39 john stultz [this message]
2003-03-11 19:40 ` john stultz
2003-03-11 21:47 ` george anzinger
2003-03-11 21:58 ` john stultz
2003-03-11 22:39 ` george anzinger
2003-03-11 22:59 ` john stultz
2003-03-11 23:44 ` george anzinger
2003-03-12 2:57 Jim Houston
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=1047411561.16614.684.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=Joel.Becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wim.coekaerts@oracle.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
all inboxes | Powered by JetHome®