mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: rusty@rustcorp.com.au
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: per_cpu fixes
Date: Wed, 9 Jul 2003 14:56:57 -0700	[thread overview]
Message-ID: <16140.36777.496398.930000@napali.hpl.hp.com> (raw)
In-Reply-To: <200307092120.h69LKTBH002759@napali.hpl.hp.com>

>>>>> On Wed, 9 Jul 2003 14:20:29 -0700, David Mosberger <davidm@linux.hpl.hp.com> said:

  David> Care needs to be taken when taking the address of a CPU-local
  David> variable, because otherwise things may break when comparing addresses
  David> on a platform which uses virtual remapping to implement such
  David> variables.  In particular, it's almost always unsafe to use the
  David> address of a per-CPU variable which contains a "struct list", because
  David> the list-manipulation routines use the list-head address to detect the
  David> end of the list etc.

  David> The patch below makes 2.5.74+ work on ia64 by reverting to the old
  David> definition of this_rq().  Ditto for kernel/timer.c.

Sorry, the original patch had an extraneous & which snuck in undetected.

Patch below should be better...

	--david

===== kernel/sched.c 1.196 vs edited =====
--- 1.196/kernel/sched.c	Wed Jul  9 11:06:25 2003
+++ edited/kernel/sched.c	Wed Jul  9 14:36:55 2003
@@ -176,7 +176,7 @@
 static DEFINE_PER_CPU(struct runqueue, runqueues);
 
 #define cpu_rq(cpu)		(&per_cpu(runqueues, (cpu)))
-#define this_rq()		(&__get_cpu_var(runqueues))
+#define this_rq()		(cpu_rq(smp_processor_id())) /* not __get_cpu_var(runqueues)! */
 #define task_rq(p)		cpu_rq(task_cpu(p))
 #define cpu_curr(cpu)		(cpu_rq(cpu)->curr)
 #define rt_task(p)		((p)->prio < MAX_RT_PRIO)
===== kernel/timer.c 1.62 vs edited =====
--- 1.62/kernel/timer.c	Wed Jul  9 11:06:25 2003
+++ edited/kernel/timer.c	Wed Jul  9 13:30:31 2003
@@ -160,7 +160,7 @@
  */
 void add_timer(struct timer_list *timer)
 {
-	tvec_base_t *base = &get_cpu_var(tvec_bases);
+	tvec_base_t *base = &per_cpu(tvec_bases, get_cpu());
   	unsigned long flags;
   
   	BUG_ON(timer_pending(timer) || !timer->function);
@@ -171,7 +171,7 @@
 	internal_add_timer(base, timer);
 	timer->base = base;
 	spin_unlock_irqrestore(&base->lock, flags);
-	put_cpu_var(tvec_bases);
+	put_cpu();
 }
 
 /***
@@ -234,7 +234,7 @@
 		return 1;
 
 	spin_lock_irqsave(&timer->lock, flags);
-	new_base = &__get_cpu_var(tvec_bases);
+	new_base = &per_cpu(tvec_bases, smp_processor_id());
 repeat:
 	old_base = timer->base;
 
@@ -792,7 +792,7 @@
  */
 static void run_timer_softirq(struct softirq_action *h)
 {
-	tvec_base_t *base = &__get_cpu_var(tvec_bases);
+	tvec_base_t *base = &per_cpu(tvec_bases, smp_processor_id());
 
 	if (time_after_eq(jiffies, base->timer_jiffies))
 		__run_timers(base);

  reply	other threads:[~2003-07-09 21:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 21:20 David Mosberger
2003-07-09 21:56 ` David Mosberger [this message]
2003-07-10  1:41 ` Rusty Russell
2003-07-10  9:37   ` Andi Kleen
2003-07-10 17:55   ` David Mosberger
2003-07-10 18:15     ` Linus Torvalds
2003-07-10 18:22       ` David Mosberger
2003-07-11  2:01     ` Rusty Russell
2003-07-11  2:08       ` David Mosberger

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=16140.36777.496398.930000@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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®