From: Vinayak Kale <vkale@apm.com>
To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: tglx@linutronix.de, will.deacon@arm.com, patches@apm.com,
jcm@redhat.com, Vinayak Kale <vkale@apm.com>
Subject: [PATCH V2 1/2] genirq: Add an accessor for IRQ_PER_CPU flag
Date: Wed, 13 Nov 2013 16:35:24 +0530 [thread overview]
Message-ID: <1384340725-26073-2-git-send-email-vkale@apm.com> (raw)
In-Reply-To: <1384340725-26073-1-git-send-email-vkale@apm.com>
This patch adds an accessor function for IRQ_PER_CPU flag.
The accessor function is useful to dertermine whether an IRQ is percpu or not.
Signed-off-by: Vinayak Kale <vkale@apm.com>
---
include/linux/irqdesc.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/linux/irqdesc.h b/include/linux/irqdesc.h
index 56fb646..acd8a3f 100644
--- a/include/linux/irqdesc.h
+++ b/include/linux/irqdesc.h
@@ -152,6 +152,14 @@ static inline int irq_balancing_disabled(unsigned int irq)
return desc->status_use_accessors & IRQ_NO_BALANCING_MASK;
}
+static inline int irq_is_percpu(unsigned int irq)
+{
+ struct irq_desc *desc;
+
+ desc = irq_to_desc(irq);
+ return (desc && (desc->status_use_accessors & IRQ_PER_CPU)) ? 1 : 0;
+}
+
static inline void
irq_set_lockdep_class(unsigned int irq, struct lock_class_key *class)
{
--
1.7.9.5
next prev parent reply other threads:[~2013-11-13 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 11:05 [PATCH V2 0/2] genirq: arm64: perf: support for percpu pmu interrupt Vinayak Kale
2013-11-13 11:05 ` Vinayak Kale [this message]
2013-11-13 14:08 ` [PATCH V2 1/2] genirq: Add an accessor for IRQ_PER_CPU flag Marc Zyngier
2013-11-14 10:31 ` Vinayak Kale
2013-11-13 11:05 ` [PATCH V2 2/2] arm64: perf: add support for percpu pmu interrupt Vinayak Kale
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=1384340725-26073-2-git-send-email-vkale@apm.com \
--to=vkale@apm.com \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@apm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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