summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2015-04-01 10:49:47 -0400
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2015-12-18 10:48:37 -0500
commit7cfb905b9638982862f0331b36ccaaca5d383b49 (patch)
treeb3b5aad877ceb60a8483cd605d56315ee67b4759 /Makefile
parenta396f3a210c3a61e94d6b87ec05a75d0be2a60d0 (diff)
downloadlinux-stable-7cfb905b9638982862f0331b36ccaaca5d383b49.tar.gz
linux-stable-7cfb905b9638982862f0331b36ccaaca5d383b49.tar.bz2
linux-stable-7cfb905b9638982862f0331b36ccaaca5d383b49.zip
xen/pciback: For XEN_PCI_OP_disable_msi[|x] only disable if device has MSI(X) enabled.
Otherwise just continue on, returning the same values as previously (return of 0, and op->result has the PIRQ value). This does not change the behavior of XEN_PCI_OP_disable_msi[|x]. The pci_disable_msi or pci_disable_msix have the checks for msi_enabled or msix_enabled so they will error out immediately. However the guest can still call these operations and cause us to disable the 'ack_intr'. That means the backend IRQ handler for the legacy interrupt will not respond to interrupts anymore. This will lead to (if the device is causing an interrupt storm) for the Linux generic code to disable the interrupt line. Naturally this will only happen if the device in question is plugged in on the motherboard on shared level interrupt GSI. This is part of XSA-157 CC: stable@vger.kernel.org Reviewed-by: David Vrabel <david.vrabel@citrix.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions