From: tip-bot for Marc Zyngier <marc.zyngier@arm.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
santosh.shilimkar@ti.com, marc.zyngier@arm.com,
tglx@linutronix.de
Subject: [tip:irq/urgent] genirq: Don't allow per cpu interrupts to be suspended
Date: Fri, 18 Nov 2011 15:48:28 -0800 [thread overview]
Message-ID: <tip-2ed0e645f358c26f4f4a7aed56a9488db0020ad1@git.kernel.org> (raw)
In-Reply-To: <1321446459-31409-1-git-send-email-marc.zyngier@arm.com>
Commit-ID: 2ed0e645f358c26f4f4a7aed56a9488db0020ad1
Gitweb: http://git.kernel.org/tip/2ed0e645f358c26f4f4a7aed56a9488db0020ad1
Author: Marc Zyngier <marc.zyngier@arm.com>
AuthorDate: Wed, 16 Nov 2011 12:27:39 +0000
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 17 Nov 2011 17:44:04 +0100
genirq: Don't allow per cpu interrupts to be suspended
The power management functions related to interrupts do not know
(yet) about per-cpu interrupts and end up calling the wrong
low-level methods to enable/disable interrupts.
This leads to all kind of interesting issues (action taken on one
CPU only, updating a refcount which is not used otherwise...).
The workaround for the time being is simply to flag these interrupts
with IRQF_NO_SUSPEND. At least on ARM, these interrupts are actually
dealt with at the architecture level.
Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Link: http://lkml.kernel.org/r/1321446459-31409-1-git-send-email-marc.zyngier@arm.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
kernel/irq/manage.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index 67ce837..0e2b179 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1596,7 +1596,7 @@ int request_percpu_irq(unsigned int irq, irq_handler_t handler,
return -ENOMEM;
action->handler = handler;
- action->flags = IRQF_PERCPU;
+ action->flags = IRQF_PERCPU | IRQF_NO_SUSPEND;
action->name = devname;
action->percpu_dev_id = dev_id;
prev parent reply other threads:[~2011-11-18 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 12:27 [PATCH REPOST] genirq: don't " Marc Zyngier
2011-11-16 14:30 ` Thomas Gleixner
2011-11-18 23:48 ` tip-bot for Marc Zyngier [this message]
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-2ed0e645f358c26f4f4a7aed56a9488db0020ad1@git.kernel.org \
--to=marc.zyngier@arm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=santosh.shilimkar@ti.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome