public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	ak@suse.de
Subject: Re: Device hang when offlining a CPU due to IRQ misrouting
Date: Tue, 19 Jun 2007 15:08:12 -0700	[thread overview]
Message-ID: <20070619220812.GG7160@linux-os.sc.intel.com> (raw)
In-Reply-To: <20070619204929.GM9751@tree.beaverton.ibm.com>

On Tue, Jun 19, 2007 at 01:49:30PM -0700, Darrick J. Wong wrote:
> 
> This fixes the problem!  Hurrah!

Great!  Andrew, please include the appended patch in -mm.

----
Subject: [patch] x86_64, irq: use mask/unmask and proper locking in fixup_irqs
From: Suresh Siddha <suresh.b.siddha@intel.com>

Force irq migration path during cpu offline, is not using proper
locks and irq_chip mask/unmask routines. This will result in
some races(especially the device generating the interrupt can see
some inconsistent state, resulting in issues like stuck irq,..).

Appended patch fixes the issue by taking proper lock and
encapsulating irq_chip set_affinity() with a mask() before and an
unmask() after.

This fixes a MSI irq stuck issue reported by Darrick Wong.

There are several more general bugs in this area(irq migration in the
process context). For example,

1. Possibility of missing edge triggered irq.
2. Reliable method of migrating level triggered irq in the process context.

We plan to look and close these in the near future.

Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Eric W. Biederman <ebiederm@xmission.com>
Reported-by: Darrick Wong <djwong@us.ibm.com>
---

diff --git a/arch/x86_64/kernel/irq.c b/arch/x86_64/kernel/irq.c
index 3eaceac..55b2733 100644
--- a/arch/x86_64/kernel/irq.c
+++ b/arch/x86_64/kernel/irq.c
@@ -144,17 +144,41 @@ void fixup_irqs(cpumask_t map)
 
 	for (irq = 0; irq < NR_IRQS; irq++) {
 		cpumask_t mask;
+		int break_affinity = 0;
+		int set_affinity = 1;
+
 		if (irq == 2)
 			continue;
 
+		/* interrupt's are disabled at this point */
+		spin_lock(&irq_desc[irq].lock);
+
+		if (!irq_has_action(irq) ||
+		    cpus_equal(irq_desc[irq].affinity, map)) {
+			spin_unlock(&irq_desc[irq].lock);
+			continue;
+		}
+
 		cpus_and(mask, irq_desc[irq].affinity, map);
-		if (any_online_cpu(mask) == NR_CPUS) {
-			printk("Breaking affinity for irq %i\n", irq);
+		if (cpus_empty(mask)) {
+			break_affinity = 1;
 			mask = map;
 		}
+
+		irq_desc[irq].chip->mask(irq);
+
 		if (irq_desc[irq].chip->set_affinity)
 			irq_desc[irq].chip->set_affinity(irq, mask);
-		else if (irq_desc[irq].action && !(warned++))
+		else if (!(warned++))
+			set_affinity = 0;
+
+		irq_desc[irq].chip->unmask(irq);
+
+		spin_unlock(&irq_desc[irq].lock);
+
+		if (break_affinity && set_affinity)
+			printk("Broke affinity for irq %i\n", irq);
+		else if (!set_affinity)
 			printk("Cannot set affinity for irq %i\n", irq);
 	}
 

  reply	other threads:[~2007-06-19 22:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  0:44 Device hang when offlining a CPU due to IRQ misrouting Darrick J. Wong
2007-06-01 19:39 ` Eric W. Biederman
2007-06-05 17:23 ` Siddha, Suresh B
2007-06-05 17:36   ` Darrick J. Wong
2007-06-05 18:13     ` Siddha, Suresh B
2007-06-05 18:33       ` Darrick J. Wong
2007-06-05 18:40         ` Siddha, Suresh B
2007-06-05 20:09           ` Darrick J. Wong
2007-06-05 21:14             ` Siddha, Suresh B
2007-06-05 23:57               ` Darrick J. Wong
2007-06-06  1:37                 ` Siddha, Suresh B
2007-06-06 18:58                   ` Darrick J. Wong
2007-06-06 19:35                     ` Siddha, Suresh B
2007-06-06 23:16                       ` Darrick J. Wong
2007-06-08  0:57                         ` Siddha, Suresh B
2007-06-18 22:38                           ` Darrick J. Wong
2007-06-18 23:54                             ` Siddha, Suresh B
2007-06-19  0:51                               ` Darrick J. Wong
2007-06-19 17:54                                 ` Eric W. Biederman
2007-06-19 18:00                                   ` Siddha, Suresh B
2007-06-19 18:55                                     ` Eric W. Biederman
2007-06-19 19:06                                     ` Darrick J. Wong
2007-06-19 19:59                                       ` Siddha, Suresh B
2007-06-19 20:49                                         ` Darrick J. Wong
2007-06-19 22:08                                           ` Siddha, Suresh B [this message]
2007-06-23 23:54                                             ` Rafael J. Wysocki
2007-06-23 23:58                                               ` Andrew Morton
2007-06-24  0:45                                                 ` Eric W. Biederman
2007-06-24  0:51                                                   ` Siddha, Suresh B
2007-06-24 12:50                                                   ` Rafael J. Wysocki
2007-06-24  0:28                                               ` Siddha, Suresh B
2007-06-24 12:48                                                 ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2007-06-01 21:57 Emmanuel Fusté
2007-06-02  0:18 ` Eric W. Biederman
2007-06-02  2:19   ` Darrick J. Wong
2007-06-02  3:48     ` Eric W. Biederman
2007-06-03 21:03 Emmanuel Fusté

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=20070619220812.GG7160@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=djwong@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox