From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: udelay() & preemption & drifty ITCs
Date: Mon, 24 Nov 2003 21:25:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106970915331863@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106955914311295@msgid-missing>
On Mon, Nov 24, 2003 at 01:00:43PM -0800, Jesse Barnes wrote:
> On Sun, Nov 23, 2003 at 02:39:29PM -0800, Jesse Barnes wrote:
> > Yep, it appears so. I guess we need a 'preempt_disable/disable()' pair
> > around the itc access. Of course, callers under a spinlock are already
> > protected, so maybe exposure to this problem isn't that large?
>
> Here's the patch. Compiles and boots, but I haven't made a test module
> that illustrates this bug, so I haven't tested it.
Here's one that actually patches the affected routine. Same caveat
applies.
Jesse
diff -Nru a/include/asm-ia64/delay.h b/include/asm-ia64/delay.h
--- a/include/asm-ia64/delay.h Mon Nov 24 14:19:19 2003
+++ b/include/asm-ia64/delay.h Mon Nov 24 14:19:19 2003
@@ -15,6 +15,7 @@
#include <linux/config.h>
#include <linux/kernel.h>
#include <linux/sched.h>
+#include <linux/preempt.h>
#include <linux/compiler.h>
#include <asm/intrinsics.h>
@@ -81,11 +82,14 @@
static __inline__ void
udelay (unsigned long usecs)
{
- unsigned long start = ia64_get_itc();
- unsigned long cycles = usecs*local_cpu_data->cyc_per_usec;
+ unsigned long start, cycles;
+ preempt_disable();
+ start = ia64_get_itc();
+ cycles = usecs*local_cpu_data->cyc_per_usec;
while (ia64_get_itc() - start < cycles)
/* skip */;
+ preempt_enable();
}
#endif /* _ASM_IA64_DELAY_H */
next prev parent reply other threads:[~2003-11-24 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 3:45 udelay() & preemption & drifty ITCs Jack Steiner
2003-11-23 22:39 ` Jesse Barnes
2003-11-24 21:00 ` Jesse Barnes
2003-11-24 21:13 ` Jesse Barnes
2003-11-24 21:25 ` Jesse Barnes [this message]
2003-11-24 22:01 ` Jack Steiner
2003-11-24 22:21 ` Jesse Barnes
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=marc-linux-ia64-106970915331863@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.