Commit 955bfe59 authored Dec 08, 2015 by Qais Yousef Committed by Thomas Gleixner Feb 25, 2016

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 <qais.yousef@imgtec.com>
Cc: <jason@lakedaemon.net>
Cc: <marc.zyngier@arm.com>
Cc: <jiang.liu@linux.intel.com>
Cc: <ralf@linux-mips.org>
Cc: <linux-mips@linux-mips.org>
Cc: <lisa.parratt@imgtec.com>
Cc: Qais Yousef <qsyousef@gmail.com>
Link: http://lkml.kernel.org/r/1449580830-23652-7-git-send-email-qais.yousef@imgtec.com


Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

parent 379b6564

include/linux/irq.h

+3 −1

Original line number	Diff line number	Diff line
		@@ -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 {