summaryrefslogtreecommitdiff
path: root/include/asm-ia64
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@hp.com>2007-01-25 05:48:04 (GMT)
committerTony Luck <tony.luck@intel.com>2007-02-05 22:09:51 (GMT)
commit451fe00cf7fd48ba55acd1c8b891e7a65e1b3f81 (patch)
treebfcdcefad73d32948fe4626af8720fc8c174b4a5 /include/asm-ia64
parent06f87adff12e52429390b22c57443665b073cd82 (diff)
downloadlinux-451fe00cf7fd48ba55acd1c8b891e7a65e1b3f81.tar.xz
[IA64] Clear IRQ affinity when unregistered
When we offline a CPU, migrate_irqs() tries to determine whether the affinity bits of the IRQ descriptor match any of the remaining online CPUs. If not, it fixes up the interrupt to point somewhere else. Unfortunately, if an IRQ is unregistered the IRQ descriptor may still have affinity to the CPU being offlined, but the no_irq_chip handler doesn't provide a set_affinity function. This causes us to hit the WARN_ON in migrate_irqs(). The easiest solution seems to be setting all the bits in the affinity mask when the last interrupt is removed from the vector. I hit this on an older kernel with Xen/ia64 using driver domains (so it probably needs more testing on upstream). Xen essentially uses the bind/unbind interface in sysfs to unregister a device from a driver and thus unregister the interrupt. Signed-off-by: Alex Williamson <alex.williamson@hp.com> Signed-off-by: Tony Luck <tony.luck@intel.com>
Diffstat (limited to 'include/asm-ia64')
0 files changed, 0 insertions, 0 deletions