From: Ingo Molnar <mingo@elte.hu>
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH] 2.6.17-rt1 : fix x86_64 oops
Date: Tue, 4 Jul 2006 08:50:24 +0200 [thread overview]
Message-ID: <20060704065024.GA5789@elte.hu> (raw)
In-Reply-To: <20060704064307.GB2752@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> > Ingo, do you have a suspect ?
>
> I suspect it's the patch below. That patch (from John) relaxes the
> affinities of IRQ threads: if there are /proc/irq/*/smp_affinity
> entries that have multiple bits set an IRQ thread is allowed to jump
> from one CPU to another while it is executing a IRQ-handler. It
> _should_ be fine but i'd not be surprised if that caused breakage ...
the patch below is against 2.6.17-rt5, does this solve the crashes?
Ingo
Index: linux-rt.q/kernel/irq/manage.c
===================================================================
--- linux-rt.q.orig/kernel/irq/manage.c
+++ linux-rt.q/kernel/irq/manage.c
@@ -645,17 +645,24 @@ extern asmlinkage void __do_softirq(void
static int curr_irq_prio = 49;
-static int do_irqd(void * __desc)
+static void follow_irq_affinity(struct irq_desc *desc)
{
- struct sched_param param = { 0, };
- struct irq_desc *desc = __desc;
#ifdef CONFIG_SMP
- int irq = desc - irq_desc;
cpumask_t mask;
- mask = cpumask_of_cpu(any_online_cpu(irq_desc[irq].affinity));
+ if (cpus_equal(current->cpus_allowed, desc->affinity))
+ return;
+ mask = cpumask_of_cpu(any_online_cpu(desc->affinity));
set_cpus_allowed(current, mask);
#endif
+}
+
+static int do_irqd(void * __desc)
+{
+ struct sched_param param = { 0, };
+ struct irq_desc *desc = __desc;
+
+ follow_irq_affinity(desc);
current->flags |= PF_NOFREEZE | PF_HARDIRQ;
/*
@@ -674,13 +681,7 @@ static int do_irqd(void * __desc)
local_irq_disable();
__do_softirq();
local_irq_enable();
-#ifdef CONFIG_SMP
- /*
- * Did IRQ affinities change?
- */
- if (!cpus_equal(current->cpus_allowed, irq_desc[irq].affinity))
- set_cpus_allowed(current, irq_desc[irq].affinity);
-#endif
+ follow_irq_affinity(desc);
schedule();
}
__set_current_state(TASK_RUNNING);
next prev parent reply other threads:[~2006-07-04 6:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 20:01 2.6.17-rt1 : x86_64 oops Dipankar Sarma
2006-06-28 18:21 ` [PATCH] 2.6.17-rt1 : fix " Dipankar Sarma
2006-06-28 19:32 ` Ingo Molnar
2006-06-28 20:02 ` Dipankar Sarma
2006-06-29 14:24 ` Ingo Molnar
2006-06-29 16:32 ` Paul E. McKenney
2006-06-29 19:41 ` Paul E. McKenney
2006-06-29 20:11 ` Ingo Molnar
2006-06-29 21:35 ` Paul E. McKenney
2006-07-03 16:57 ` Dipankar Sarma
2006-07-04 4:15 ` Dipankar Sarma
2006-07-04 6:43 ` Ingo Molnar
2006-07-04 6:50 ` Ingo Molnar [this message]
2006-07-05 9:11 ` Dipankar Sarma
2006-07-26 7:36 ` Dipankar Sarma
2006-07-06 20:06 ` Paul E. McKenney
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=20060704065024.GA5789@elte.hu \
--to=mingo@elte.hu \
--cc=dipankar@in.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.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 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.