summaryrefslogtreecommitdiff
path: root/include/xen/interface
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2011-10-17 11:46:06 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2012-01-25 13:53:19 -0800
commitc3914e688d696bdda2b2df0b56df1ecba59bbfab (patch)
tree28ed951f4ef5c0cc2f5fb4d07a44e201e4f25d37 /include/xen/interface
parent8e1ac7852f2f42a04f983e4692b4f88451b14f66 (diff)
PCI: msi: Disable msi interrupts when we initialize a pci device
commit a776c491ca5e38c26d9f66923ff574d041e747f4 upstream. I traced a nasty kexec on panic boot failure to the fact that we had screaming msi interrupts and we were not disabling the msi messages at kernel startup. The booting kernel had not enabled those interupts so was not prepared to handle them. I can see no reason why we would ever want to leave the msi interrupts enabled at boot if something else has enabled those interrupts. The pci spec specifies that msi interrupts should be off by default. Drivers are expected to enable the msi interrupts if they want to use them. Our interrupt handling code reprograms the interrupt handlers at boot and will not be be able to do anything useful with an unexpected interrupt. This patch applies cleanly all of the way back to 2.6.32 where I noticed the problem. Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include/xen/interface')
0 files changed, 0 insertions, 0 deletions