Suresh Siddha <suresh.b.siddha@intel.com> writes:

quoted text
> Generic infrastructure for migrating the irq from the process context in the
> presence of CONFIG_GENERIC_PENDING_IRQ.
>
> This will be used later for migrating irq in the presence of
> interrupt-remapping.

Why the API difference between IRQ_MOVE_PCNTXT set affinity handlers and
!CONFIG_GENERIC_PENDING_IRQ handlers?


quoted text
>  #ifdef CONFIG_GENERIC_PENDING_IRQ
> -	set_pending_irq(irq, cpumask);
> +	if (desc->status & IRQ_MOVE_PCNTXT) {
> +		unsigned long flags;
> +
> +		spin_lock_irqsave(&desc->lock, flags);
> +		desc->chip->set_affinity(irq, cpumask);
> +		spin_unlock_irqrestore(&desc->lock, flags);
> +	} else
> +		set_pending_irq(irq, cpumask);
>  #else
>  	desc->affinity = cpumask;
>  	desc->chip->set_affinity(irq, cpumask);
>
> -- 
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/