aboutsummaryrefslogtreecommitdiff
path: root/security
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2008-11-28 09:51:23 +0000
committerPaul Mackerras <paulus@samba.org>2008-12-01 09:40:18 +1100
commitcc353c30bbdb84f4317a6c149ebb11cde2232e40 (patch)
tree114558272ac12498546e3b19ba069a21e153a40f /security
parentd015fe9951641b2d869a7ae4a690be2a05a9dc7f (diff)
powerpc/mpic: Don't reset affinity for secondary MPIC on boot
Kexec/kdump currently fails on the IBM QS2x blades when the kexec happens on a CPU other than the initial boot CPU. It turns out that this is the result of mpic_init trying to set affinity of each interrupt vector to the current boot CPU. As far as I can tell, the same problem is likely to exist on any secondary MPIC, because they have to deliver interrupts to the first output all the time. There are two potential solutions for this: either not set up affinity at all for secondary MPICs, or assume that a single CPU output is connected to the upstream interrupt controller and hardcode affinity to that per architecture. This patch implements the second approach, defaulting to the first output. Currently, all known secondary MPICs are routed to their upstream port using the first destination, so we hardcode that. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions