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: 12 Jun 2003 12:39:55 -0700 [thread overview]
Message-ID: <1055446795.18644.148.camel@w-jstultz2.beaverton.ibm.com> (raw)
In-Reply-To: <1055440030.1043.7.camel@serpentine.internal.keyresearch.com>
On Thu, 2003-06-12 at 10:47, Bryan O'Sullivan wrote:
> On Wed, 2003-06-11 at 17:33, john stultz wrote:
>
> > Let me know if you have any issues with this patch.
>
> Thanks, John. Your updated patch has survived some beating on my test
> systems. I've also applied Vojtech's fix to hpet_tick.
One little tweak, you're still subtracting tick_usec when calculating
offset. Doesn't cause any major problems since you're catching error
with the offset<0 switch. However we won't catch lost interrupts
properly if we're always negative.
thanks
-john
Patch for that should be:
--- 1.22/arch/x86_64/kernel/time.c Thu Jun 12 11:40:33 2003
+++ edited/arch/x86_64/kernel/time.c Thu Jun 12 11:42:43 2003
@@ -254,7 +254,7 @@
vxtime.last = offset;
} else {
offset = (((tsc - vxtime.last_tsc) *
- vxtime.tsc_quot) >> 32) - tick_usec;
+ vxtime.tsc_quot) >> 32) - (USEC_PER_SEC / HZ);
if (offset < 0)
offset = 0;
next prev parent reply other threads:[~2003-06-12 19:31 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 [this message]
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
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=1055446795.18644.148.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®