Commit-ID:  955bfe5912e7839abcc83694f06867535487404b
Gitweb:     http://git.kernel.org/tip/955bfe5912e7839abcc83694f06867535487404b
Author:     Qais Yousef <[email protected]>
AuthorDate: Tue, 8 Dec 2015 13:20:17 +0000
Committer:  Thomas Gleixner <[email protected]>
CommitDate: Thu, 25 Feb 2016 10:56:55 +0100

genirq: Add an extra comment about the use of affinity in irq_common_data

Affinity will have dual meaning depends on the type of the irq. If it is
a normal irq, it'll have the standard affinity meaning.

If it is an IPI, it will hold the mask of the cpus to which an IPI can be
sent.

Signed-off-by: Qais Yousef <[email protected]>
Cc: <[email protected]>
Cc: <[email protected]>
Cc: <[email protected]>
Cc: <[email protected]>
Cc: <[email protected]>
Cc: <[email protected]>
Cc: Qais Yousef <[email protected]>
Link: 
http://lkml.kernel.org/r/[email protected]
Signed-off-by: Thomas Gleixner <[email protected]>
---
 include/linux/irq.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/include/linux/irq.h b/include/linux/irq.h
index 3c1c967..0817afd 100644
--- a/include/linux/irq.h
+++ b/include/linux/irq.h
@@ -133,7 +133,9 @@ struct irq_domain;
  *                     Use accessor functions to deal with it
  * @node:              node index useful for balancing
  * @handler_data:      per-IRQ data for the irq_chip methods
- * @affinity:          IRQ affinity on SMP
+ * @affinity:          IRQ affinity on SMP. If this is an IPI
+ *                     related irq, then this is the mask of the
+ *                     CPUs to which an IPI can be sent.
  * @msi_desc:          MSI descriptor
  */
 struct irq_common_data {

Reply via email to