From: "tip-bot for Tian, Kevin" <kevin.tian@intel.com>
To: linux-tip-commits@vger.kernel.org
Cc: kevin.tian@intel.com, xen-devel@lists.xensource.com,
Ian.Campbell@citrix.com, fengzhe.zhang@intel.com,
JBeulich@novell.com, mingo@redhat.com, hpa@zytor.com,
tglx@linutronix.de
Subject: [tip:x86/irq] x86: Skip migrating IRQF_PER_CPU irqs in fixup_irqs()
Date: Thu, 19 May 2011 12:55:06 GMT [thread overview]
Message-ID: <tip-b87ba87ca26e226b2277a2d5613ed596f408e96d@git.kernel.org> (raw)
Commit-ID: b87ba87ca26e226b2277a2d5613ed596f408e96d
Gitweb: http://git.kernel.org/tip/b87ba87ca26e226b2277a2d5613ed596f408e96d
Author: Tian, Kevin <kevin.tian@intel.com>
AuthorDate: Fri, 6 May 2011 14:43:36 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 19 May 2011 14:51:08 +0200
x86: Skip migrating IRQF_PER_CPU irqs in fixup_irqs()
IRQF_PER_CPU means that the irq cannot be moved away from a given
cpu. So it must not be migrated when the cpu goes offline.
[ tglx: massaged changelog ]
Signed-off-by: Fengzhe Zhang <fengzhe.zhang@intel.com>
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Link: http://lkml.kernel.org/r/%3C625BA99ED14B2D499DC4E29D8138F1505C8ED7F7E2%40shsmsx502.ccr.corp.intel.com%3E
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
arch/x86/kernel/irq.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
index 1cb0b9f..544efe2 100644
--- a/arch/x86/kernel/irq.c
+++ b/arch/x86/kernel/irq.c
@@ -249,7 +249,7 @@ void fixup_irqs(void)
data = irq_desc_get_irq_data(desc);
affinity = data->affinity;
- if (!irq_has_action(irq) ||
+ if (!irq_has_action(irq) || irqd_is_per_cpu(data) ||
cpumask_subset(affinity, cpu_online_mask)) {
raw_spin_unlock(&desc->lock);
continue;
reply other threads:[~2011-05-19 12:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tip-b87ba87ca26e226b2277a2d5613ed596f408e96d@git.kernel.org \
--to=kevin.tian@intel.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@novell.com \
--cc=fengzhe.zhang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).