All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: udelay() & preemption & drifty ITCs
Date: Mon, 24 Nov 2003 21:00:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106970777429946@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106955914311295@msgid-missing>

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.

Jesse

diff -Nru a/include/asm-ia64/delay.h b/include/asm-ia64/delay.h
--- a/include/asm-ia64/delay.h	Mon Nov 24 13:59:12 2003
+++ b/include/asm-ia64/delay.h	Mon Nov 24 13:59:12 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>
@@ -32,8 +33,10 @@
 {
 	unsigned long result;
 
+	preempt_disable();
 	result = ia64_getreg(_IA64_REG_CR_ITM);
 	ia64_srlz_d();
+	preempt_enable();
 	return result;
 }
 

  parent reply	other threads:[~2003-11-24 21:00 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 [this message]
2003-11-24 21:13 ` Jesse Barnes
2003-11-24 21:25 ` Jesse Barnes
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-106970777429946@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.