From: john stultz <johnstul@us.ibm.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Andi Kleen <ak@suse.de>,
vojtech@suse.cz, discuss@x86-64.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] New x86_64 time code for 2.5.70
Date: 11 Jun 2003 13:44:47 -0700 [thread overview]
Message-ID: <1055364287.18643.59.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <1055357432.17154.77.camel@serpentine.internal.keyresearch.com>
On Wed, 2003-06-11 at 11:50, Bryan O'Sullivan wrote:
> I've forward-ported Vojtech's time code from 2.4, fixing some locking
> along the way. The new code supports using the AMD8111 HPET for time
> calculations. It also works stably with the PIT/TSC on every boot,
> which is the source of the time problems in current 2.5.
Oh drat, you beat me to it! I've been working on the very same thing.
This is very much needed, so thanks for doing this.
> Right now, the only known problem is with the fixup of jiffies if a
> timer interrupt is lost, which I've hence turned off. There's
> preliminary support for using HPET for the gettimeofday vsyscall, but
> since vsyscalls are disabled on x86-64 for now, that's obviously
> untested.
I'll start testing your patch and I'll see if I can't fixup the lost
tick compensation.
thanks!
-john
next prev parent reply other threads:[~2003-06-11 20:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 18:50 Bryan O'Sullivan
2003-06-11 19:18 ` Andi Kleen
2003-06-11 19:56 ` Bryan O'Sullivan
2003-06-11 20:10 ` Bryan O'Sullivan
2003-06-11 21:23 ` john stultz
2003-06-11 21:36 ` Bryan O'Sullivan
2003-06-11 21:41 ` john stultz
2003-06-12 0:33 ` john stultz
2003-06-12 6:40 ` Vojtech Pavlik
2003-06-12 17:47 ` Bryan O'Sullivan
2003-06-12 19:39 ` john stultz
2003-06-12 19:55 ` Vojtech Pavlik
2003-06-12 21:16 ` Bryan O'Sullivan
2003-06-13 1:43 ` john stultz
2003-06-12 19:48 ` Vojtech Pavlik
2003-06-11 20:41 ` Vojtech Pavlik
2003-06-11 20:44 ` john stultz [this message]
2003-06-11 21:32 ` Mika Penttilä
2003-06-11 21:28 ` Bryan O'Sullivan
2003-06-12 4:40 ` [discuss] " Andreas Jaeger
2003-06-12 6:42 ` Vojtech Pavlik
2003-06-12 6:47 ` Vojtech Pavlik
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=1055364287.18643.59.camel@w-jstultz2.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=ak@suse.de \
--cc=bos@serpentine.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®