From: Chuck Ebbert <76306.1226@compuserve.com>
To: Ray Lee <madrabbit@gmail.com>
Cc: Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@brodo.de>,
John Stultz <johnstul@us.ibm.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>
Subject: [patch] fix delay_tsc (was Re: delay_tsc(): inefficient delay loop (2.6.16-mm1))
Date: Sun, 26 Mar 2006 16:44:45 -0500 [thread overview]
Message-ID: <200603261647_MC3-1-BB98-CB09@compuserve.com> (raw)
In-Reply-To: <2c0942db0603240922u7bade58lcf2a6af2af8ec6ae@mail.gmail.com>
On Fri, 24 Mar 2006 09:22:51 -0800, Ray Lee wrote:
> On 3/24/06, Andreas Mohr <andi@rhlx01.fht-esslingen.de> wrote:
> > + loops += bclock;
> [...]
> > - } while ((now-bclock) < loops);
> > + } while (now < loops);
>
> Erm, aren't you introducing an overflow problem here?
>
> if loops is 2^32-1, bclock is 1, the old version would execute the
> proper number of times, the new one will blow out in one tick.
Yes, but the old version has a bug too. I don't have 2.6.16-mm1, but
in 2.6.16 it's in arch/i386/kernel/timers/timer_tsc.c and
arch/x86_64/lib/delay.c:
static void delay_tsc(unsigned long loops)
{
unsigned long bclock, now;
rdtscl(bclock);
do
{
rep_nop();
rdtscl(now);
} while ((now-bclock) < loops);
}
If (loops == 100000) and (bclock == 2^32-1) the loop will terminate
immediately when the low part of the TSC overflows because (now-bclock)
is a large number. That can't be right...
I'm running a system with this applied now. I think there are still
problems if someone uses huge delays, though. What keeps someone from
trying to delay for > 2^31 cycles?
i386 delay_tsc() will truncate delays when the TSC is within 'loops'
of overflow. We must be able to handle TSC overflow both before and
after 'end', i.e. [1], [2] and [3] below.
zero
|
case A (end < start) start [1] | [2] end [3]
|
case B (end > start) start [1] end [2] | [3]
Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
--- 2.6.16-d2.orig/arch/i386/kernel/timers/timer_tsc.c
+++ 2.6.16-d2/arch/i386/kernel/timers/timer_tsc.c
@@ -170,14 +170,22 @@ unsigned long long sched_clock(void)
static void delay_tsc(unsigned long loops)
{
- unsigned long bclock, now;
+ unsigned long start, end, now;
- rdtscl(bclock);
- do
- {
- rep_nop();
- rdtscl(now);
- } while ((now-bclock) < loops);
+ rdtscl(start);
+ end = start + loops;
+
+ if (unlikely(end < start)) {
+ do {
+ rep_nop();
+ rdtscl(now);
+ } while (now > start || now < end);
+ } else {
+ do {
+ rep_nop();
+ rdtscl(now);
+ } while (now > start && now < end);
+ }
}
#ifdef CONFIG_HPET_TIMER
--
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
next reply other threads:[~2006-03-26 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:44 Chuck Ebbert [this message]
2006-03-26 23:18 ` Andi Kleen
2006-03-27 0:42 ` Ray Lee
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=200603261647_MC3-1-BB98-CB09@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=madrabbit@gmail.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®