[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m13amhgwx8.fsf@frodo.ebiederm.org>
Date: Thu, 10 Jul 2008 16:08:03 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: mingo@...e.hu, hpa@...or.com, tglx@...utronix.de,
akpm@...ux-foundation.org, arjan@...ux.intel.com,
andi@...stfloor.org, ebiederm@...ssion.com,
jbarnes@...tuousgeek.org, steiner@....com,
linux-kernel@...r.kernel.org
Subject: Re: [patch 11/26] x64, x2apic/intr-remap: generic irq migration support from process context
Suresh Siddha <suresh.b.siddha@...el.com> writes:
> 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?
> #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);
>
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists